Advanced CodeQL repeatedly becomes disabled_manually in an active LoopWorkspace fork; no corresponding security-log events #213468
Unanswered
nickolbp21-web
asked this question in
Actions
Replies: 1 comment
|
💬 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. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Workflow Configuration
Discussion Details
Summary
Please route this to GitHub Actions / Code Scanning engineering to determine whether a backend job or platform policy is disabling a custom security-analysis workflow in a LoopWorkspace fork. Re-enabling works, but does not last. This is not a request to bypass a platform restriction: if a restriction is intentional, please identify its scope and the supported way to keep security analysis running.
Repository: https://github.com/nickolbp21-web/LoopWorkspace
Workflow: https://github.com/nickolbp21-web/LoopWorkspace/actions/workflows/codeql-security.yml
Workflow ID:
418869019; path:.github/workflows/codeql-security.yml.Expected and actual behavior
The approved advanced CodeQL workflow should stay enabled for push, pull request, weekly schedule and manual dispatch. It performs unsigned simulator analysis of Swift plus Actions and Ruby; it does not sign or distribute an app.
The workflow repeatedly changes from
activetodisabled_manually. Both the owner's CLI and a separate read-only GitHub App observe the same state and provider timestamp. Recurrences have often fallen near minutes 11, 31 and 51. Successful analysis does not prevent the next disable.Recent provider timestamps:
Latest successful scan: https://github.com/nickolbp21-web/LoopWorkspace/actions/runs/44105820916, attempt 2, completed 2026-11-18 09:55:10 UTC. Actual Swift, Actions and Ruby analyses match main
13ec86699942492fdee825c11b53459d0129d2f7with empty error fields. The first attempt's separate macOS runner-acquisition failure was recovered.Current settings and investigation
enabled:true,allowed_actions:all.state:not-configured; no attached security configuration (HTTP 204), no repository rulesets.action:workflows.disable_workflowwith the full repository qualifier and a date-filtered query since November 16.Closely related upstream evidence
This investigation found a report in the same fork network where a contributor identifies GitHub Admin as the disabling actor: LoopKit/LoopWorkspace#461 (comment) . The maintainer's copy test also records continued disabling of the old workflow after schedule removal: LoopKit/LoopWorkspace#461 (comment) . Current upstream documentation says the replacement filename was later disabled too: https://loopkit.github.io/loopdocs/browser/automatic/ .
Those reports concern Build Loop, not this custom CodeQL scanner. A shared cause is a hypothesis, not an established fact. Please check whether a LoopWorkspace fork-network rule or background process is also matching security-analysis workflows.
Separate inconsistent generated-run records
Generated default workflow
406399527still has four queued runs with zero jobs/artifacts:43674957405,43674809665,41772033216,41753859143. Normal/force cancellation returned 409, deletion returned 403, and UI cancellation failed. Other users report the same signature in https://github.com/orgs/community/discussions/212964 . Two of these records predate November 11; I am not attributing all four to that incident or asserting they cause the repeated disabling.Requested engineering action
Private support has received the detailed reproduction but no technical response yet. This report includes only public repository/run metadata and sanitized observations. No credentials, IP addresses, private logs or homelab details are included.
All reactions