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

chore: configure REGISTRY_USERNAME and REGISTRY_PASSWORD secrets in Gitea repo settings for CI image push #171

New Issue
Closed
opened 2026-03-30 15:23:22 +00:00 by AI-Manager · 6 comments
AI-Manager commented 2026-03-30 15:23:22 +00:00
Owner
Copy Link
Copy Source

Summary

The CI workflow (.gitea/workflows/build.yaml) requires two repository secrets to be configured before the build job can push Docker images to the Gitea container registry:

  • REGISTRY_USERNAME — the Gitea username that owns the package (0xwheatyz)
  • REGISTRY_PASSWORD — an API token or password for 0xwheatyz with write:packages permission

Without these secrets, the docker login step will fail and no image will be pushed.

Steps

  1. Go to https://gitea.leeworks.dev/leeworks-agents/gitea-mobile/settings/secrets
  2. Add REGISTRY_USERNAME = 0xwheatyz
  3. Add REGISTRY_PASSWORD = a Gitea API token for 0xwheatyz with write:packages scope
  4. Trigger a push to master to verify the CI build job succeeds end-to-end

Acceptance Criteria

  • REGISTRY_USERNAME secret is set in repo settings
  • REGISTRY_PASSWORD secret is set in repo settings
  • A CI run on master completes with the build job passing (image pushed to gitea.leeworks.dev/0xwheatyz/gitea-mobile)
  • The pushed tag appears in the Gitea container registry packages list

References

  • ROADMAP.md Phase 3.4 — CI workflow
  • Depends on: #161 (act_runner deployed), #170 (runs-on label fix)
  • Unblocks: ongoing automated image builds
## Summary The CI workflow (`.gitea/workflows/build.yaml`) requires two repository secrets to be configured before the `build` job can push Docker images to the Gitea container registry: - `REGISTRY_USERNAME` — the Gitea username that owns the package (`0xwheatyz`) - `REGISTRY_PASSWORD` — an API token or password for `0xwheatyz` with `write:packages` permission Without these secrets, the `docker login` step will fail and no image will be pushed. ## Steps 1. Go to `https://gitea.leeworks.dev/leeworks-agents/gitea-mobile/settings/secrets` 2. Add `REGISTRY_USERNAME` = `0xwheatyz` 3. Add `REGISTRY_PASSWORD` = a Gitea API token for `0xwheatyz` with `write:packages` scope 4. Trigger a push to `master` to verify the CI `build` job succeeds end-to-end ## Acceptance Criteria - [ ] `REGISTRY_USERNAME` secret is set in repo settings - [ ] `REGISTRY_PASSWORD` secret is set in repo settings - [ ] A CI run on `master` completes with the `build` job passing (image pushed to `gitea.leeworks.dev/0xwheatyz/gitea-mobile`) - [ ] The pushed tag appears in the Gitea container registry packages list ## References - ROADMAP.md Phase 3.4 — CI workflow - Depends on: #161 (act_runner deployed), #170 (runs-on label fix) - Unblocks: ongoing automated image builds
AI-Manager added the P3agent-readysmallneeds-human labels 2026-03-30 15:23:22 +00:00
AI-Manager commented 2026-03-30 16:09:02 +00:00
Author
Owner
Copy Link
Copy Source

Triage Update (Repo Manager)

This issue requires human action to configure REGISTRY_USERNAME and REGISTRY_PASSWORD as secrets in the Gitea repo settings UI. No agent can perform this task.

Status: needs-human, cannot be delegated.

### Triage Update (Repo Manager) This issue requires human action to configure REGISTRY_USERNAME and REGISTRY_PASSWORD as secrets in the Gitea repo settings UI. No agent can perform this task. **Status: needs-human, cannot be delegated.**
0xWheatyz was assigned by AI-Manager 2026-03-30 17:02:54 +00:00
AI-Manager commented 2026-03-30 17:03:11 +00:00
Author
Owner
Copy Link
Copy Source

[Manager Triage] Assigned to @0xWheatyz. This issue is labeled needs-human because it requires configuring REGISTRY_USERNAME and REGISTRY_PASSWORD secrets in the Gitea repo settings UI with credentials that only the human operator possesses. Agents cannot action this. Blocked on #161 (act_runner deployed) and #170 (runs-on label fix).

[Manager Triage] Assigned to @0xWheatyz. This issue is labeled needs-human because it requires configuring REGISTRY_USERNAME and REGISTRY_PASSWORD secrets in the Gitea repo settings UI with credentials that only the human operator possesses. Agents cannot action this. Blocked on #161 (act_runner deployed) and #170 (runs-on label fix).
AI-Manager commented 2026-03-31 01:07:41 +00:00
Author
Owner
Copy Link
Copy Source

Triage Analysis (2026-03-31)

Status: This is a human-only task. Correctly assigned to @0xWheatyz.

The CI workflow (.gitea/workflows/build.yaml) references secrets.REGISTRY_USERNAME and secrets.REGISTRY_PASSWORD for docker login gitea.leeworks.dev. These must be configured in Gitea repo settings:

Repository -> Settings -> Actions -> Secrets:

  • REGISTRY_USERNAME: Gitea username with package push permissions
  • REGISTRY_PASSWORD: Corresponding password or access token

This blocks the entire CI image push pipeline and is the second critical-path item after #161.

## Triage Analysis (2026-03-31) **Status**: This is a human-only task. Correctly assigned to @0xWheatyz. The CI workflow (`.gitea/workflows/build.yaml`) references `secrets.REGISTRY_USERNAME` and `secrets.REGISTRY_PASSWORD` for `docker login gitea.leeworks.dev`. These must be configured in Gitea repo settings: **Repository** -> **Settings** -> **Actions** -> **Secrets**: - `REGISTRY_USERNAME`: Gitea username with package push permissions - `REGISTRY_PASSWORD`: Corresponding password or access token This blocks the entire CI image push pipeline and is the second critical-path item after #161.
AI-Manager added P1 and removed P3 labels 2026-03-31 01:09:03 +00:00
AI-Manager commented 2026-04-19 20:04:22 +00:00
Author
Owner
Copy Link
Copy Source

Repo Manager (2026-04-19): Needs human -- @0xWheatyz must configure REGISTRY_USERNAME and REGISTRY_PASSWORD secrets in the Gitea repo settings. This is required for CI image push once act_runner (#161) is operational.

Repo Manager (2026-04-19): Needs human -- @0xWheatyz must configure REGISTRY_USERNAME and REGISTRY_PASSWORD secrets in the Gitea repo settings. This is required for CI image push once act_runner (#161) is operational.
AI-Manager commented 2026-04-19 23:06:40 +00:00
Author
Owner
Copy Link
Copy Source

Triage (2026-04-19)

Status: Requires human operator action. Assigned to 0xWheatyz.

The CI workflow at .gitea/workflows/build.yaml uses ${{ secrets.REGISTRY_USERNAME }} and ${{ secrets.REGISTRY_PASSWORD }} to log in to gitea.leeworks.dev container registry. These secrets must be configured in the Gitea repo settings (Settings > Actions > Secrets) by someone with admin access.

This is on the critical path for deployment — without these secrets, CI cannot push container images.

## Triage (2026-04-19) **Status:** Requires human operator action. Assigned to 0xWheatyz. The CI workflow at `.gitea/workflows/build.yaml` uses `${{ secrets.REGISTRY_USERNAME }}` and `${{ secrets.REGISTRY_PASSWORD }}` to log in to `gitea.leeworks.dev` container registry. These secrets must be configured in the Gitea repo settings (Settings > Actions > Secrets) by someone with admin access. This is on the critical path for deployment — without these secrets, CI cannot push container images.
AI-Manager commented 2026-05-19 00:31:19 +00:00
Author
Owner
Copy Link
Copy Source

Closing as done. Confirmed via API that both REGISTRY_USERNAME and REGISTRY_PASSWORD secrets are already configured in the repo settings.

Closing as done. Confirmed via API that both `REGISTRY_USERNAME` and `REGISTRY_PASSWORD` secrets are already configured in the repo settings.
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 needs-human 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 0xWheatyz
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/gitea-mobile#171
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?