When selecting a self-hosted runner in a GitHub Actions workflow using the runs-on attribute, you can only choose a runner by its labels or group, not by the name of the runner itself.

When selecting a self-hosted runner in a GitHub Actions workflow using the runs-on attribute, you can only choose a runner by its labels or group, not by the name of the runner itself.

I want to add manually triggered workflow_dispatch to GitHub actions as follows:

I’m working with two GitHub Actions workflow files: one for a SHARED-PROJECT and one for a DEPENDANT-PROJECT. I’m trying to trigger the DEPENDANT-PROJECT workflow using workflow_run whenever there’s a change in SHARED-PROJECT. However, I’m encountering an issue where the DEPENDANT-PROJECT workflow is not being triggered when there’s a change in the SHARED-PROJECT.

I’m working with two GitHub Actions workflow files: one for a SHARED-PROJECT and one for a DEPENDANT-PROJECT. I’m trying to trigger the DEPENDANT-PROJECT workflow using workflow_run whenever there’s a change in SHARED-PROJECT. However, I’m encountering an issue where the DEPENDANT-PROJECT workflow is not being triggered when there’s a change in the SHARED-PROJECT.

I have a GitHub Actions workflow that I currently run on push, but I can also run it ad hoc and on a cron schedule.

I have a GitHub Actions workflow that I currently run on push, but I can also run it ad hoc and on a cron schedule.

I am downloading a zip using curl in github workflow and storing the same in same repository in folder abc/xyz.

I am trying to create a workflow to backup files in my local repository: once per day, add everything that changed, create a commit and push it to main.

I want to add secrets to build-push-action by names. This is how I done with one secret: