GitHub Community
Action not triggered, neither on pull request, nor on push #26572
-
|
fossasia/open-event-server#6476 Added an action and pushed to a branch and created a pull request. No action got triggered. Does the name of the workflow YML have any role in the process? I suppose not. However, I’ll try to merge it in the default branch and see if it changes anything. However, I tried just creating a PR in private repo 3 days ago and it worked without the workflow committed to the default branch. Also, when I go to checks panel of the pull request, it just hangs on Waiting for checks information… https://github.com/fossasia/open-event-server/pull/6476/checks |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
|
Still, no trigger https://github.com/fossasia/open-event-server/actions When I went here, it said “Re-enable actions for this repository”, “e had problems enabling actions for this repo … normally this can be fixed by just re-enabling” I re-enabled them and updated a few PRs, but no action has been triggered |
Beta Was this translation helpful? Give feedback.
-
|
Seems like Actions were disabled in organization. So, I had to enable them in organization settings and then enable it in repository settings. I think it should be apparent to the user and shown that actions are not enabled for the repository or organization and at which level |
Beta Was this translation helpful? Give feedback.
-
|
When actions are disabled for an organization or repo the Actions tab should be hidden the repo. Are you still seeing the Actions tab and workflows are not running? |
Beta Was this translation helpful? Give feedback.
-
|
No, the action tab was hidden, but I thought it was a bug in the extension I was using, so I appended /actions in the repo URL to access the section |
Beta Was this translation helpful? Give feedback.
-
|
You have to actually click on the Actions tab in order to explicitly see the executing Action. Otherwise, the Pull Request screen doesn’t always show them. |
Beta Was this translation helpful? Give feedback.
Seems like Actions were disabled in organization. So, I had to enable them in organization settings and then enable it in repository settings.
I think it should be apparent to the user and shown that actions are not enabled for the repository or organization and at which level