Run checks when adding a commit to a PR with github actions

[pvanderlinden]

Select Topic Area

Question

Body

I'm running into an issue when adding a commit to a PR with Github Actions, as it doesn't run any workflows for that commit. The documentation says this is by default, which I understand. But this is causing issues with PR's as checks won't be displayed in the merge section of the PR interface (or the checks tab). This would make it easy to overlook failed checls, and also prevent the PR to be merged in case of rules (as the checks don't pass (there arent any)).

I found a work around, but it includes adding a deploy key to (each) repository, and use that key to commit to the repository. This feels like a hack, and I'm probably doing something wrong?

The exact scenario is actually coming from a closed issue on dependabot-core: bumping the version of your repository (package.json/pyproject.toml/etc) for Dependabot PR's with github actions: dependabot/dependabot-core#2048 (comment)

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[jsoref]

You aren't doing anything wrong. You have found a correct approach.

A reason for the design that @github-actions doesn't itself trigger workflows is that there's a risk of someone writing a workflow that would effectively eat its own tail -- iteratively triggering itself forever.