CI Action workflow not running on push on branch of fork. Possible bug?

[arf20]

Select Topic Area

Question

Body

The repo in question is https://github.com/arf20/SuWidgets
There is a workflow in /.github/workflows/ci.yml at 'develop' branch. This workflow does run in the original repo.
I don't get it, this is very similar to what I have done in https://github.com/arf20/suscan, it does work there.
Thank you.

[airtower-luna]

You might need to enable actions for the repository in the settings. When you create a fork of a repository that contains actions they'll be disabled by default, to make sure they don't run unless you actually want them to.

[arf20]

I am positive that this is enabled already.

[airtower-luna]

Can you check the Actions tab? When I go there on certain forks of mine I'm asked if I want to enable the workflows.

[arf20]

The action tab shows this, like if it didn't get the workflow
I'm not asked to enable actions, its just empty

[aignermax]

I have exactly the same problem I think.
I have forked a github action and suggested some changes to it.
now the original auther asked me to test my fork of the github workflow before she can be sure it works.
but I cannot use my forked github repo as a step of an action in a github workflow because:
when I do, github really uses the original source code instead of my forked one.

here is my fork: https://github.com/aignermax/setup-godot
and the workflow file that tries to use it:
https://github.com/aignermax/GodotPCKDemo/blob/main/.github/workflows/Build_Exe.yaml

Did you somehow find a solution to this problem?

I might test that a bit more..

[Edit] the solution for me was to look carefully into the package.json und build and also package the code as shown in my comment below. [/Edit]

[shakefu]

Hitting this same problem. Do forked repositories not allow their own GitHub Actions runs?

[aignermax]

so I had found the solution for my problem and it turns out I had simply not compiled the package properly.. it was written in Typescript and you have to look into the package.json to see the defined commands there.
In my case it was nothing more than basically calling

npm run all

and only then could I use the github action.

[shakefu]

For folks who land here for the same idiot reason I did: The UI/UX is awful. There is no Setting in "Settings" of a Forked repository to enable GitHub Actions.

You have to go to the Actions tab and then there will be a banner saying, "Blah blah this is forked, do you want to run stuff?"

Just UI/UX shenanigans. Someone @github should make sure that the banner shows up in the Settings > Actions page.

[transmissions11]

good answer

[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! 💬

[cratelyn]

i also encountered this issue today. the ux was confusing to me as well.

[gbakeman]

I also had issues with my workflows not running in a repository I forked/cloned. My situation may have been unique since I turned on GH Pages deployments before I started fiddling with the rest of my workflows, so I think something glitched in GitHub's UI that prevented it from alerting me that Actions were disabled. What GitHub support advised I do is remove my workflow files (move elsewhere on my PC), commit, re-add files, and commit again. Workflows working fine now.

[micheljung]

This saved my day! Definitely a bug.

[royfrancis]

This solution worked for me too.

[tiagosiebler]

Seems the push event does not trigger for forks anymore, not on newer repos (but still on older repos)...very strange. Adding the pull_request event seems to trigger it in that scenario:

on:
  push:
  pull_request: