Adds inline comments to all three continue-on-error: true deploy steps in .forgejo/workflows/deploy.yml
Explains that each step is best-effort and requires SSH_PRIVATE_KEY; a missing secret causes a soft step failure (orange in UI) while the overall job stays green — this is intentional
The continue-on-error: true flag makes a failing step appear as orange/failed in the step list but does not propagate the failure to the job, so the overall CI run shows green. Without an explanation this looks like a bug. The comments document that this is by design: deployment to the server is best-effort and should not block the CI green light when SSH credentials are absent.
Test plan
CI passes on this branch (no code logic changed, only YAML comments)
## Summary
- Adds inline comments to all three `continue-on-error: true` deploy steps in `.forgejo/workflows/deploy.yml`
- Explains that each step is best-effort and requires `SSH_PRIVATE_KEY`; a missing secret causes a soft step failure (orange in UI) while the overall job stays green — this is intentional
- Closes the confusion reported in issue #154
## Why these comments matter
The `continue-on-error: true` flag makes a failing step appear as orange/failed in the step list but does not propagate the failure to the job, so the overall CI run shows green. Without an explanation this looks like a bug. The comments document that this is by design: deployment to the server is best-effort and should not block the CI green light when SSH credentials are absent.
## Test plan
- [ ] CI passes on this branch (no code logic changed, only YAML comments)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
continue-on-error: truedeploy steps in.forgejo/workflows/deploy.ymlSSH_PRIVATE_KEY; a missing secret causes a soft step failure (orange in UI) while the overall job stays green — this is intentionalWhy these comments matter
The
continue-on-error: trueflag makes a failing step appear as orange/failed in the step list but does not propagate the failure to the job, so the overall CI run shows green. Without an explanation this looks like a bug. The comments document that this is by design: deployment to the server is best-effort and should not block the CI green light when SSH credentials are absent.Test plan