GitHub Actions workflow not running on push – what am I missing? #189654
-
Why are you starting this discussion?Bug What GitHub Actions topic or product is this about?Workflow Deployment Discussion DetailsHi everyone, My ./github/workflows/main.yml looks roughly like this: But when I push to main, nothing shows up under Actions for this repo. What are the common things I should check to make sure the workflow actually runs? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
A few quick things to double‑check when a workflow won’t run: The file is in the exact path: .github/workflows/anything.yml (no extra folders, correct spelling). The on.push.branches value matches your real branch name (main vs master etc.). The workflow file is committed to the default branch (or the branch you’re pushing to), not only sitting in a different branch. Workflows are not disabled for the repo/org (check the Actions tab → settings). After fixing any of these, make one more commit and push again – that usually makes the workflow appear and start running. |
Beta Was this translation helpful? Give feedback.
A few quick things to double‑check when a workflow won’t run:
The file is in the exact path: .github/workflows/anything.yml (no extra folders, correct spelling).
The on.push.branches value matches your real branch name (main vs master etc.).
The workflow file is committed to the default branch (or the branch you’re pushing to), not only sitting in a different branch.
Workflows are not disabled for the repo/org (check the Actions tab → settings).
After fixing any of these, make one more commit and push again – that usually makes the workflow appear and start running.