Stanford CS342 - Building for Digital Health
[Technical Questions] Can't trigger the expected GitHub Actions workflow for new commit #122
-
In what area do you have a technical challenge?Other (non-StanfordBDHG-related) area DescriptionHi, I noticed that my recent push to my branch (sixian) did not trigger the expected GitHub Actions workflow for automated testing. Previously, every push would automatically start a test run, but now it only runs when I manually trigger it from the Actions tab. And my manual workflows were canceled automatically. I haven't changed anything in my .github/workflows/ folder recently. Do you have any suggestions on why this might be happening and how I can fix it? Thanks, Reproductionlink to my branch: https://github.com/CS342/2025-NeutroFeverGuard/tree/sixian Expected behaviorNone Additional contextNo response Code of Conduct
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
My "Beta Deployment" workflow is not automatically canceled. And I see that the "Beta Deployment" includes "Static Analysis" and "Build and Test". So is running "Beta Deployment" all I need? |
Beta Was this translation helpful? Give feedback.
-
|
Yes that should work. The build and test workflow should run the automatic testing. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! It works now. |
Beta Was this translation helpful? Give feedback.
Yes that should work. The build and test workflow should run the automatic testing.