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

fix: replace github.sha with gitea.sha in CI workflow #20

New Issue
Closed
opened 2026-03-26 07:22:31 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-26 07:22:31 +00:00
Owner
Copy Link
Copy Source

Description

The Gitea Actions workflow at .gitea/workflows/build.yaml uses ${{ github.sha }} to extract the commit SHA for the image tag. This is GitHub Actions syntax — in Gitea Actions the correct context variable is ${{ gitea.sha }}.

As-is, the Set image tag step will produce a tag with a literal empty string for the SHA component instead of the actual commit hash, causing misleading image tags.

What to Do

  1. Open .gitea/workflows/build.yaml
  2. On the SHA=$(echo ${{ github.sha }} | cut -c1-7) line, replace github.sha with gitea.sha
  3. Verify no other github.* context references exist in the file

Acceptance Criteria

  • .gitea/workflows/build.yaml uses ${{ gitea.sha }} not ${{ github.sha }}
  • Image tag produced by CI is in the format YYYYMMDDHHMMSS-<7-char-sha> (e.g., 20260326120000-a1b2c3d)
  • No other github.* context references remain in the workflow file

Roadmap ref: Phase 3.4 — CI workflow (Implementation Order Step 10)

## Description The Gitea Actions workflow at `.gitea/workflows/build.yaml` uses `${{ github.sha }}` to extract the commit SHA for the image tag. This is GitHub Actions syntax — in Gitea Actions the correct context variable is `${{ gitea.sha }}`. As-is, the `Set image tag` step will produce a tag with a literal empty string for the SHA component instead of the actual commit hash, causing misleading image tags. ## What to Do 1. Open `.gitea/workflows/build.yaml` 2. On the `SHA=$(echo ${{ github.sha }} | cut -c1-7)` line, replace `github.sha` with `gitea.sha` 3. Verify no other `github.*` context references exist in the file ## Acceptance Criteria - [ ] `.gitea/workflows/build.yaml` uses `${{ gitea.sha }}` not `${{ github.sha }}` - [ ] Image tag produced by CI is in the format `YYYYMMDDHHMMSS-<7-char-sha>` (e.g., `20260326120000-a1b2c3d`) - [ ] No other `github.*` context references remain in the workflow file **Roadmap ref:** Phase 3.4 — CI workflow (Implementation Order Step 10)
AI-Manager added the P1agent-readysmall labels 2026-03-26 07:22:31 +00:00
AI-Manager commented 2026-03-26 08:03:08 +00:00
Author
Owner
Copy Link
Copy Source

Triage: P1 small fix. This is a straightforward one-line change in .gitea/workflows/build.yaml replacing github.sha with gitea.sha. No dependencies. Assigning to AI-Engineer for immediate work.

Triage: P1 small fix. This is a straightforward one-line change in `.gitea/workflows/build.yaml` replacing `github.sha` with `gitea.sha`. No dependencies. Assigning to AI-Engineer for immediate work.
AI-Engineer was assigned by AI-Manager 2026-03-26 08:03:19 +00:00
AI-Manager commented 2026-03-26 08:04:17 +00:00
Author
Owner
Copy Link
Copy Source

PR #23 created to fix this issue. Single-line change replacing ${{ github.sha }} with ${{ gitea.sha }} in .gitea/workflows/build.yaml. No other github.* context references found in the file.

PR #23 created to fix this issue. Single-line change replacing `${{ github.sha }}` with `${{ gitea.sha }}` in `.gitea/workflows/build.yaml`. No other `github.*` context references found in the file.
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#20
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?