ldraney/pal-e-platform
1
0
Fork 0
Code Issues 91 Pull requests 5 Projects Releases Packages Wiki Activity Actions

Create ldraney user on Forgejo for public-facing profile URL #237

New issue
Closed
opened 2026-03-28 21:42:55 +00:00 by forgejo_admin · 1 comment
forgejo_admin commented 2026-03-28 21:42:55 +00:00
Contributor
Copy link

Type

Feature

Lineage

  • Board: board-pal-e-platform
  • Story: story:portfolio
  • Arch: arch:forgejo

Repo

forgejo_admin/pal-e-platform

User Story

As Lucas, I want a ldraney user on Forgejo so my public profile URL is forgejo.tail5b443a.ts.net/ldraney instead of forgejo.tail5b443a.ts.net/forgejo_admin — which looks like a default admin account on a resume.

Context

The resume links to the Forgejo profile for portfolio repos. forgejo_admin is the only user and owns all repos. Need either a new ldraney user with repos forked/transferred, or an org rename, or at minimum a redirect.

File Targets

  • Forgejo admin API — create user or rename (no file change, API operation)
  • ~/resume-playground/index.html — update profile URL after change
  • Woodpecker repo configs — may need owner update if repos are transferred

Acceptance Criteria

  • forgejo.tail5b443a.ts.net/ldraney resolves to a profile with portfolio repos visible
  • Resume HTML updated to use the new URL
  • Public repos accessible under the new username

Test Expectations

  • curl -sI https://forgejo.tail5b443a.ts.net/ldraney — returns 200
  • Resume link works
  • CI pipelines still trigger on push

Constraints

  • Investigate options: new user + repo transfer, org rename, or URL alias
  • Don't break existing CI pipelines that reference forgejo_admin
  • May need to update Woodpecker repo configs if owner changes

Checklist

  • Decide approach
  • Implement
  • Update resume URL
  • Verify CI still works

Related

  • forgejo_admin/resume-playground#1 — resume project
### Type Feature ### Lineage - Board: board-pal-e-platform - Story: story:portfolio - Arch: arch:forgejo ### Repo `forgejo_admin/pal-e-platform` ### User Story As Lucas, I want a `ldraney` user on Forgejo so my public profile URL is `forgejo.tail5b443a.ts.net/ldraney` instead of `forgejo.tail5b443a.ts.net/forgejo_admin` — which looks like a default admin account on a resume. ### Context The resume links to the Forgejo profile for portfolio repos. `forgejo_admin` is the only user and owns all repos. Need either a new `ldraney` user with repos forked/transferred, or an org rename, or at minimum a redirect. ### File Targets - Forgejo admin API — create user or rename (no file change, API operation) - `~/resume-playground/index.html` — update profile URL after change - Woodpecker repo configs — may need owner update if repos are transferred ### Acceptance Criteria - [ ] `forgejo.tail5b443a.ts.net/ldraney` resolves to a profile with portfolio repos visible - [ ] Resume HTML updated to use the new URL - [ ] Public repos accessible under the new username ### Test Expectations - [ ] `curl -sI https://forgejo.tail5b443a.ts.net/ldraney` — returns 200 - [ ] Resume link works - [ ] CI pipelines still trigger on push ### Constraints - Investigate options: new user + repo transfer, org rename, or URL alias - Don't break existing CI pipelines that reference forgejo_admin - May need to update Woodpecker repo configs if owner changes ### Checklist - [ ] Decide approach - [ ] Implement - [ ] Update resume URL - [ ] Verify CI still works ### Related - `forgejo_admin/resume-playground#1` — resume project
forgejo_admin commented 2026-03-28 21:47:00 +00:00
Author
Contributor
Copy link

Scope Review: NEEDS_REFINEMENT

Review note: review-621-2026-03-28

Blast radius is critical -- forgejo_admin appears in 20+ files across 8+ repos (CI pipelines, terraform, scripts, PyPI, docs). Implementation approach is undecided.

  • [SCOPE] Must decide approach (new user + transfer, rename, or alias) before scoping implementation. Recommend a spike.
  • [BODY] "Woodpecker repo configs" is vague -- needs explicit list of 6 affected repos.
  • [BODY] Missing 4 acceptance criteria: CI pipelines, terraform state, PyPI index, ArgoCD.
  • [BODY] Undocumented dependencies: pal-e-services terraform, pal-e-docs forgejo_client, basketball-api PyPI.
  • [DECOMPOSE] 20+ files, 8+ repos, 7+ AC, undecided approach. Recommend spike first, then decomposition via template-board.
## Scope Review: NEEDS_REFINEMENT Review note: `review-621-2026-03-28` Blast radius is critical -- `forgejo_admin` appears in 20+ files across 8+ repos (CI pipelines, terraform, scripts, PyPI, docs). Implementation approach is undecided. - **[SCOPE]** Must decide approach (new user + transfer, rename, or alias) before scoping implementation. Recommend a spike. - **[BODY]** "Woodpecker repo configs" is vague -- needs explicit list of 6 affected repos. - **[BODY]** Missing 4 acceptance criteria: CI pipelines, terraform state, PyPI index, ArgoCD. - **[BODY]** Undocumented dependencies: pal-e-services terraform, pal-e-docs forgejo_client, basketball-api PyPI. - **[DECOMPOSE]** 20+ files, 8+ repos, 7+ AC, undecided approach. Recommend spike first, then decomposition via template-board.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
fix-gem-bin-path
netpol-westside-ror
fix-woodpecker-multi-pipeline
345-harbor-mobile-css
290-payment-pipeline-observability
spec-board-centric-renderer
284-fix-add-pal-e-docs-namespace-to-postgres
284-add-pal-e-docs-postgres-netpol
188-cross-repo-worktree-isolation-for-parall
111-fix-keycloak-probe
86-fix-rotate-woodpecker-api-token-in-salt
71-feat-deploy-pyrra-slo-manager-with-servi
64-hotfix-woodpecker-oauth-login-broken-for
18-fix-grafana-duplicate-default-datasource-v2
18-fix-grafana-duplicate-default-datasource
13-fix-cnpg-all-parameters
No results found.
Labels
Clear labels   
domain:backend

   
domain:devops

   
domain:frontend

   
status:approved

QA passed, awaiting merge approval

  
status:in-progress

Dev agent is actively working

  
status:needs-fix

QA found issues, back to dev

  
status:qa

PR submitted, awaiting QA review

  
type:bug

Bug fix

  
type:devops

Infrastructure/CI/config work

  
type:feature

New functionality

No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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
ldraney/pal-e-platform#237
No description provided.