AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 15 Bitcoin

Add Forgejo Actions workflows mirroring GitHub CI

Public commit record

What the developer wrote

Authored by Matt Corallo

78/100 · Adequate
Add Forgejo Actions workflows mirroring GitHub CI

Port the GitHub Actions workflows under .github/workflows/ to Forgejo
Actions under .forgejo/workflows/, targeting the instance at
git.rust-bitcoin.org and the lightningdevkit/rust-lightning repo. All
jobs run on the debian-trixie worker label; the build matrix restores
windows/macos legs (no runners provisioned for those yet).

Forgejo-specific adaptations:
- Fold the fuzz corpus push into the fuzz job, since Forgejo supports
neither the workflow_run trigger nor cross-run artifact access. The
push still targets the GitHub corpus repo and is best-effort so a
push hiccup cannot cascade to dependent jobs.
- Report build failures and stale-unicode notices via the fj CLI
against Forgejo instead of the gh CLI against GitHub.
- Run cargo audit directly in place of the rustsec/audit-check action,
which is not on Forgejo's default action registry.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit adds new Forgejo-based CI/CD workflow files that mirror the project's existing GitHub Actions. It does not change any application code, cryptographic logic, or user-facing behavior. It is purely an infrastructure change to run the same tests and checks on a different CI platform.

Recommended action

No security action required. Review the new CI files as normal infrastructure maintenance; ensure secrets such as CORPUS_PUSH_TOKEN and FORGEJO_TOKEN are scoped appropriately in the Forgejo instance.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 15/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 0/15
Confidence 10/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.