How to trigger a workflow once merge-schedule-action has completed?

[panduit-bilb]

Does anyone know how to trigger a workflow after the pull_request has been merged using this action? I have tried on: push, which doesn't work in this case. I've also tried using workflow_run; however, it runs once when building the schedule and running the schedule. I want to run a workflow after the schedule merges the code into a branch.

[gr2m]

Events triggered by actions using the GITHUB_TOKEN secret don’t trigger other actions. You have to create a new repository secret with a personal access token for your account, and use that instead

[panduit-bilb]

Would this be in addition to the GITHUB_TOKEN?

[panduit-bilb]

The action I want to trigger

[gr2m]

No, you'd do this

         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.MY_SECRET }}

[panduit-bilb]

would I need to change it in both actions or just the action I want to trigger on push?

[gr2m]

both your screenshots show the same thing, or am I missing something?

You have to set GITHUB_TOKEN to ${{ secrets.MY_SECRET }} in the workflow that is performing the push, so that other GitHub Actions triggered by the push event

[panduit-bilb]

This is my yaml file

I pass a secret using a GitHub app

[panduit-bilb]

If I use my credentials vs a GitHub app

[gr2m]

what is the MY_APP secret set to?

Can you enable debug logs? Create the ACTIONS_STEP_DEBUG secret and set it to true

[panduit-bilb]

I created a GitHub App and generated a secret. When I use my PAT it complained about not being an app.

[gr2m]

I'm a bit confused by this right now. I'm swamped with other urgent work, but I'll get back to you.

I created a GitHub App and generated a secret

A GitHub App Secret cannot be used as a substitute for GITHUB_SECRET. It's used to generate a JWT (JSON Web Token) and only used for a few REST API endpoints, such as for creating an installation access token

[antonversal]

It looks like a personal access token does not work, I get an error:

Schedule date found: "2021-09-15T10:00:00.000Z"
Warning: Unhandled Rejection at:
Warning: {}
Error: HttpError: You must authenticate via a GitHub App.

Is there a workaround?

[hynjnk]

It looks similar to this issue. actions/github-script#118 (comment)

wave The Checks API is only available to GitHub Apps, so you'd need to use a separate GitHub App token rather than a PAT if you wanted to replace github-token for any Checks API calls.

See https://docs.github.com/en/rest/reference/checks for more info.****

I think these errors are made when create checks using with a personal access token.

lib/handle_pull_request.js

  const { data } = await octokit.checks.create({
    owner: eventPayload.repository.owner.login,
    repo: eventPayload.repository.name,
    name: "Merge Schedule",
    head_sha: eventPayload.pull_request.head.sha,
    status: "in_progress",
    output: {
      title: `Scheduled to be merged on ${datestring}`,
      summary: "TO BE DONE: add useful summary",
    },
  });
  core.info(`Check run created: ${data.html_url}`);

[ruisaraiva19]

@panduit-bilb @antonversal @hynjnk We just released version 2 which no longer uses status checks in favor of comments on pull requests.

By using comments for providing feedback on pull requests, the HttpError: You must authenticate via a GitHub App error thrown when using a custom access token (PAT) is gone.

Can you test with version 2 (@v2)?