fix(ci): standardize step-output writes to use FORGEJO_OUTPUT fallback #755

Closed
opened 2026-06-08 23:07:57 +02:00 by ollama · 1 comment
Collaborator

Spec sources (whitelist)

  • .forgejo/workflows/base-is-main.yml — bare $GITHUB_OUTPUT usage
  • .forgejo/workflows/w8-uptime-kuma-runtime-pilot.yml — same
  • .forgejo/workflows/merged-in-main-audit.yml — same
  • .forgejo/workflows/platformctl-auto-apply.yml — same
  • .forgejo/workflows/canary-required.yml — reference: already uses ${FORGEJO_OUTPUT:-$GITHUB_OUTPUT} (correct)
  • .forgejo/workflows/patchwarden-client-dry-run.yml — reference: already uses correct pattern

Extracted context

4 workflow files write bare $GITHUB_OUTPUT:

echo "key=value" >> $GITHUB_OUTPUT

The cross-platform pattern used by canary-required.yml and patchwarden-client-dry-run.yml is:

echo "key=value" >> ${FORGEJO_OUTPUT:-$GITHUB_OUTPUT}

This ensures compatibility with both GitHub and Forgejo runners.

Scope

In all 4 workflow files, replace bare $GITHUB_OUTPUT with ${FORGEJO_OUTPUT:-$GITHUB_OUTPUT}.

Search pattern (to verify count): rg '\$GITHUB_OUTPUT' .forgejo/workflows/ --include '*.yml' | grep -v FORGEJO_OUTPUT

Acceptance criteria

  • 0 bare $GITHUB_OUTPUT references (without FORGEJO_OUTPUT fallback)
  • All references use ${FORGEJO_OUTPUT:-$GITHUB_OUTPUT}
  • Workflow YAML still syntactically valid

Do NOT read

  • Full repo — only the 6 files listed above

Agent notes

  • Recommended executor: Gemini 3.5 Flash
  • Size: Trivial (~8 LOC)
  • Review tier: tier/trivial
  • Audit ref: state/audit/deepseek-2026-06-08-multiperspective.md §D3
  • This is a subset of #729 item 2 (claude's deslop issue)
## Spec sources (whitelist) - `.forgejo/workflows/base-is-main.yml` — bare `$GITHUB_OUTPUT` usage - `.forgejo/workflows/w8-uptime-kuma-runtime-pilot.yml` — same - `.forgejo/workflows/merged-in-main-audit.yml` — same - `.forgejo/workflows/platformctl-auto-apply.yml` — same - `.forgejo/workflows/canary-required.yml` — reference: already uses `${FORGEJO_OUTPUT:-$GITHUB_OUTPUT}` (correct) - `.forgejo/workflows/patchwarden-client-dry-run.yml` — reference: already uses correct pattern ## Extracted context 4 workflow files write bare `$GITHUB_OUTPUT`: ```yaml echo "key=value" >> $GITHUB_OUTPUT ``` The cross-platform pattern used by canary-required.yml and patchwarden-client-dry-run.yml is: ```yaml echo "key=value" >> ${FORGEJO_OUTPUT:-$GITHUB_OUTPUT} ``` This ensures compatibility with both GitHub and Forgejo runners. ## Scope In all 4 workflow files, replace bare `$GITHUB_OUTPUT` with `${FORGEJO_OUTPUT:-$GITHUB_OUTPUT}`. Search pattern (to verify count): `rg '\$GITHUB_OUTPUT' .forgejo/workflows/ --include '*.yml' | grep -v FORGEJO_OUTPUT` ## Acceptance criteria - [ ] 0 bare `$GITHUB_OUTPUT` references (without FORGEJO_OUTPUT fallback) - [ ] All references use `${FORGEJO_OUTPUT:-$GITHUB_OUTPUT}` - [ ] Workflow YAML still syntactically valid ## Do NOT read - Full repo — only the 6 files listed above ## Agent notes - Recommended executor: Gemini 3.5 Flash - Size: Trivial (~8 LOC) - Review tier: tier/trivial - Audit ref: state/audit/deepseek-2026-06-08-multiperspective.md §D3 - This is a subset of #729 item 2 (claude's deslop issue)
Owner

Closing as already implemented on current main. Evidence: workflow writes now use ; targeted scan for bare writes without FORGEJO_OUTPUT returned no matches. Verification: full platformctl test suite passed with UV_CACHE_DIR=/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane --extra dev pytest control-plane/platformctl/tests -q -> 756 passed.

Closing as already implemented on current main. Evidence: workflow writes now use ``; targeted scan for bare `` writes without `FORGEJO_OUTPUT` returned no matches. Verification: full `platformctl` test suite passed with `UV_CACHE_DIR=/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane --extra dev pytest control-plane/platformctl/tests -q` -> `756 passed`.
Sign in to join this conversation.
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform#755
No description provided.