[Upstream #174] CIs failing

[quangdang46]

Mirrored from upstream 1jehuang/jcode — Issue #174 by @rehan1020
Original state: open
Created: 2026-05-08T11:34:56Z · Updated: 2026-05-08T11:34:56Z
This issue is an auto-mirrored copy. Comments and edits here are local to quangdang46/jcode — do not expect them to propagate upstream.

---

Just opened the repo for the first time to learn about this project and use but saw that few CI's are failing please fix them.

[quangdang46]

Mirrored upstream report "CIs failing". The fork's CI configuration is independent of upstream's (.github/workflows/ci.yml). Local CI status should be checked against the fork's runs, not upstream's. Closing as not planned — file fork-specific CI failures separately.

[quangdang46]

Verified-fixed in master via PR #196.

.github/workflows/ci.yml lines 30-33 + 84+ now gate every webfactory/ssh-agent step on if: ${{ secrets.DEPLOY_KEY != '' }}, so forks without that secret don't fail the workflow at the SSH-key step. The remaining red CI you see is the actual cargo/clippy stages on a fork that doesn't yet have DEPLOY_KEY configured for cargo git deps — that's a separate fork-secrets issue, not a CI workflow bug.