Additional push in a Dependabot PR does not trigger actions

[nak3]

/area test-and-release
/kind bug

As got the answerd in https://github.com/orgs/community/discussions/62346 (Thanks @kvmware), we need to use Personal Access Token or GitHub App token to trigger github action when dependabot sends additional PR (after running hack script).

Should we add a "Personal Access Token" or "GitHub App token" for this? Or is there any other ideas?

Note There is one workaround which we can close&re-open the dependabot to trigger the githubaction.

[krsna-m]

The Github app token would be preferable

[knative-prow]

@nak3: The label(s) area/test-and-release cannot be applied, because the repository doesn't have them.

In response to this:

/area test-and-release
/kind bug

As got the answerd in https://github.com/orgs/community/discussions/62346 (Thanks @kvmware), we need to use Personal Access Token or GitHub App token to trigger github action when dependabot sends additional PR (after running hack script).

Should we add a "Personal Access Token" or "GitHub App token" for this? Or is there any other ideas?

Note There is one workaround which we can close&re-open the dependabot to trigger the githubaction.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dprotaso]

/assign @kvmware

Can we look into using the prow bot's token (the one that does cherry-picks to also do these PR changes) ?

[krsna-m]

Yes, but I still think reusing a github app would be better even if it is prow's. @upodroid Do you have a suggestion?

Notes:

• Action in question is https://github.com/knative/pkg/blob/main/.github/workflows/knative-dependabot.yaml
• example github app approach https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/making-authenticated-api-requests-with-a-github-app-in-a-github-actions-workflow

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[dprotaso]

@krsna-m is there any action here? seems like there was no resolution based on the discussion above

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.