Auto-merge will not trigger other workflows about fetch-metadata HOT 5 CLOSED

This is the expected behavior when using the GITHUB_TOKEN. You can use a PAT or a GitHub App if you want the merge to still trigger workflows. I'm doing it with a GitHub App now since I don't want to use a PAT, especially for workflows in orgs. Here's an example workflow and instructions.

from fetch-metadata.

Thanks for the example @xt0rted. Yeah I figured that would be the case. I was mainly just wondering why the examples here use GITHUB_TOKEN and if there's a way to have dependabot merge the PR and trigger other workflows without using another bot/account.

from fetch-metadata.

This is definitely confusing, since we'd expect dependency updates that get approved and merge to automatically go through CD-deploy.

When is the right time to use the PAT? Is it on the review-approve API call? or on the "enable auto-merge" API call?

from fetch-metadata.

When is the right time to use the PAT?

The workflow provided token can be used anywhere except for an action that would trigger another workflow. So in this instance you'd want to use a PAT or GitHub App Token to enable the auto-merge, but everywhere else you can use GITHUB_TOKEN.

from fetch-metadata.

Based on #162 there doesn't seem to be a good alternative to using a PAT at this time...

from fetch-metadata.