Jordan Harband 77fca77ddd [actions] fall back to the canonical nvmrc submodule when a fork lacks its own ...

Upstream's `.gitmodules` uses a relative submodule url (`../nvmrc.git`),
which resolves against the superproject's origin:
on a fork without its own `nvmrc` fork that is `<owner>/nvmrc`,
which 404s and fails `actions/checkout` with `submodules: true`.
Keep `submodules: true` (so a fork's own `nvmrc` is used when present),
but mark checkout `continue-on-error` and, only when it failed,
re-point the submodule at `nvm-sh/nvmrc` and update.

2026-06-04 09:22:04 -07:00

..

ISSUE_TEMPLATE

[meta] disable blank issues

2024-11-04 15:07:16 +00:00

workflows

[actions] fall back to the canonical nvmrc submodule when a fork lacks its own

2026-06-04 09:22:04 -07:00

external-threat-actor.png

[security] add threat model

2023-11-15 10:10:29 -08:00

FUNDING.yml

[meta] create FUNDING.yml

2019-11-05 12:05:09 -08:00

INCIDENT_RESPONSE_PLAN.md

[meta] update security policy; add IRP

2025-06-23 16:11:48 -07:00

insider-threat-actor-and-libs.png

[security] add threat model

2023-11-15 10:10:29 -08:00

SECURITY.md

[security] add security escalation policy

2025-09-15 14:33:37 +02:00

THREAT_MODEL.md

[security] fix typo in threat model

2023-12-15 09:46:35 -08:00