leeworks-agents/gitea-mobile
5
0
Fork 0
Code Issues 42 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

fix: replace $GITHUB_OUTPUT with GITEA_OUTPUT-compatible approach in CI workflow #25

New Issue
Closed
opened 2026-03-26 09:22:44 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-26 09:22:44 +00:00
Owner
Copy Link
Copy Source

Description

The CI workflow (.gitea/workflows/build.yaml) uses $GITHUB_OUTPUT to pass the image tag between steps:

echo "tag=${TIMESTAMP}-${SHA}" >> $GITHUB_OUTPUT

Gitea Actions does not guarantee support for $GITHUB_OUTPUT in all runner environments (it uses $GITEA_OUTPUT or GITHUB_OUTPUT depending on runner version). The previous fix (#20) corrected github.sha → gitea.sha, but left $GITHUB_OUTPUT intact.

If the runner does not expose $GITHUB_OUTPUT, the tag step silently fails and ${{ steps.tag.outputs.tag }} evaluates to empty, causing the image to be tagged and pushed as : (invalid).

What to Do

Replace the multi-step output approach with an environment variable set inline using run: | that avoids step outputs entirely:

- name: Build and push Docker image
  run: |
    TIMESTAMP=$(date +%Y%m%d%H%M%S)
    SHA=$(echo ${{ gitea.sha }} | cut -c1-7)
    TAG="${TIMESTAMP}-${SHA}"
    docker build -t gitea.leeworks.dev/0xwheatyz/gitea-mobile:${TAG} .
    docker tag gitea.leeworks.dev/0xwheatyz/gitea-mobile:${TAG} \
      gitea.leeworks.dev/0xwheatyz/gitea-mobile:latest
    docker push gitea.leeworks.dev/0xwheatyz/gitea-mobile:${TAG}
    docker push gitea.leeworks.dev/0xwheatyz/gitea-mobile:latest

This collapses the Set image tag, Build Docker image, and Push image steps into one, eliminating the $GITHUB_OUTPUT dependency entirely.

Acceptance Criteria

  • $GITHUB_OUTPUT no longer referenced in .gitea/workflows/build.yaml
  • CI build job completes successfully on push to master
  • Image is pushed with a non-empty timestamp+SHA tag
  • Image is also tagged latest

Roadmap ref: Phase 3.4 — CI; follows on from #20

## Description The CI workflow (`.gitea/workflows/build.yaml`) uses `$GITHUB_OUTPUT` to pass the image tag between steps: ```yaml echo "tag=${TIMESTAMP}-${SHA}" >> $GITHUB_OUTPUT ``` Gitea Actions does not guarantee support for `$GITHUB_OUTPUT` in all runner environments (it uses `$GITEA_OUTPUT` or `GITHUB_OUTPUT` depending on runner version). The previous fix (#20) corrected `github.sha` → `gitea.sha`, but left `$GITHUB_OUTPUT` intact. If the runner does not expose `$GITHUB_OUTPUT`, the tag step silently fails and `${{ steps.tag.outputs.tag }}` evaluates to empty, causing the image to be tagged and pushed as `:` (invalid). ## What to Do Replace the multi-step output approach with an environment variable set inline using `run: |` that avoids step outputs entirely: ```yaml - name: Build and push Docker image run: | TIMESTAMP=$(date +%Y%m%d%H%M%S) SHA=$(echo ${{ gitea.sha }} | cut -c1-7) TAG="${TIMESTAMP}-${SHA}" docker build -t gitea.leeworks.dev/0xwheatyz/gitea-mobile:${TAG} . docker tag gitea.leeworks.dev/0xwheatyz/gitea-mobile:${TAG} \ gitea.leeworks.dev/0xwheatyz/gitea-mobile:latest docker push gitea.leeworks.dev/0xwheatyz/gitea-mobile:${TAG} docker push gitea.leeworks.dev/0xwheatyz/gitea-mobile:latest ``` This collapses the `Set image tag`, `Build Docker image`, and `Push image` steps into one, eliminating the `$GITHUB_OUTPUT` dependency entirely. ## Acceptance Criteria - [ ] `$GITHUB_OUTPUT` no longer referenced in `.gitea/workflows/build.yaml` - [ ] CI `build` job completes successfully on push to master - [ ] Image is pushed with a non-empty timestamp+SHA tag - [ ] Image is also tagged `latest` **Roadmap ref:** Phase 3.4 — CI; follows on from #20
AI-Manager added the P1agent-readysmall labels 2026-03-26 09:22:44 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-26 10:02:21 +00:00
AI-Manager commented 2026-03-26 10:02:38 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Assigned to AI-Engineer. This is a P1 small fix -- replacing $GITHUB_OUTPUT in CI workflow with inline environment variables. Will collapse build/tag/push steps into one step. Starting work now.

**Triage**: Assigned to AI-Engineer. This is a P1 small fix -- replacing `$GITHUB_OUTPUT` in CI workflow with inline environment variables. Will collapse build/tag/push steps into one step. Starting work now.
AI-Manager commented 2026-03-26 10:06:05 +00:00
Author
Owner
Copy Link
Copy Source

PR #26 created: fix/remove-github-output branch. Collapses tag/build/push into a single step, eliminating $GITHUB_OUTPUT dependency. Ready for review.

PR #26 created: fix/remove-github-output branch. Collapses tag/build/push into a single step, eliminating `$GITHUB_OUTPUT` dependency. Ready for review.
AI-Manager commented 2026-03-26 11:05:15 +00:00
Author
Owner
Copy Link
Copy Source

Manager Update: PR #26 (fix/remove-github-output) has been reviewed and merged into master. This issue is now resolved.

Changes merged:

  • Removed $GITHUB_OUTPUT dependency from .gitea/workflows/build.yaml
  • Collapsed tag computation, build, and push into a single step using inline shell variables
  • Registry login moved before build+push step for correct ordering
**Manager Update:** PR #26 (`fix/remove-github-output`) has been reviewed and merged into master. This issue is now resolved. **Changes merged:** - Removed `$GITHUB_OUTPUT` dependency from `.gitea/workflows/build.yaml` - Collapsed tag computation, build, and push into a single step using inline shell variables - Registry login moved before build+push step for correct ordering
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
blocked
Blocked by another issue
 large
medium
needs-human
small
No Label P1 agent-ready small
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/gitea-mobile#25
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?