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
Teach /release to trigger the release-git workflow
This concludes the transition of Git for Windows' release process off of
Azure Pipelines onto GitHub workflows.
The added code is a bit more verbose than the previous one because we
have to do all the hard work of maintaining the Check Run in the
git-for-windows/git PR manually.
This is actually a net improvement over the previous situation, where
there was _no_ update in that PR whatsoever as to the current state of
the release.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
elseif(tagGitWorkflowRunID!==gitVersionMatch[3])thrownewError(`The 'git-artifacts' runs are based on different 'tag-git' runs`)
356
+
}else{
357
+
thrownewError(`The '${workflowName}' run was not found`)
358
+
}
359
+
}
360
+
361
+
awaitupdateCheckRun(
362
+
context,
363
+
awaitgetToken(),
364
+
owner,
365
+
repo,
366
+
releaseCheckRunId,{
367
+
output: {
368
+
title: `Publish ${gitVersion} for @${commitSHA}`,
369
+
summary: `Downloading the Git artifacts from ${workFlowRunIDs['x86_64']} and ${workFlowRunIDs['i686']} and publishing them as a new GitHub Release at ${owner}/${repo}`
0 commit comments