You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying v2.46.1, trying to publish the release _and_ creating the
discussion failed like this:
FAILED GitHub REST API call!
{
port: 443,
hostname: 'api.github.com',
method: 'PATCH',
path: '/repos/git-for-windows/git/releases/175612508',
headers: {
'User-Agent': 'GitForWindowsHelperApp/0.0',
Accept: 'application/json',
{
statusCode: 404,
statusMessage: 'Not Found',
body: '{"message":"Discussion could not be created. Make sure you passed a valid category name.","documentation_url":"https://docs.github.com/rest/releases/releases#update-a-release","status":"404"}',
json: {
message: 'Discussion could not be created. Make sure you passed a valid category name.',
documentation_url: 'https://docs.github.com/rest/releases/releases#update-a-release',
status: '404'
}
}
Authorization: '***',
'Content-Type': 'application/json',
'Content-Length': 96
}
}
Culprit: The GitForWindowsHelper GitHub App, with whose permissions this
was run, lacked the permission to create Discussions.
The release was published, though...
So let's separate those two steps, publishing a draft release, and
adding the discussion, and do not fail the deployment if the Discussion
could not be created.
Signed-off-by: Johannes Schindelin <[email protected]>
0 commit comments