Skip to content

Commit 781302e

Browse files
committed
upload-snapshot: queue the Check Run using a valid token
The `getToken()` method does not need any parameters when being called in `slash-commands.js` because there, the `owner`/`repo` values are obvious. But when triggering an `upload-snapshot` workflow, we are juggling three different repositories, therefore we absolutely need to specify for which repository the token needs to target. This was the _actual_ reason why the `upload-snapshot` run was not triggered after v2.48.1 was released, the conclusions I drew in #124 were incorrect. Signed-off-by: Johannes Schindelin <[email protected]>
1 parent 15d08ea commit 781302e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

GitForWindowsHelper/cascading-runs.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -354,7 +354,7 @@ const handlePush = async (context, req) => {
354354
const tagGitCheckRunTitle = `Upload snapshot Git @${commit}`
355355
const tagGitCheckRunId = await queueCheckRun(
356356
context,
357-
await getToken(),
357+
await getToken(context, pushOwner, pushRepo),
358358
pushOwner,
359359
pushRepo,
360360
commit,

0 commit comments

Comments
 (0)