Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 6 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Interactive profile setup menu for canonical Gitea MCP config #31

New Issue
Closed
opened 2026-07-01 22:26:46 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-01 22:26:46 -05:00
Owner
Copy Link
Copy Source

Parent

Roadmap #10. Depends on #19 / PR #30 (canonical runtime profiles).

Problem

Hand-editing the canonical profiles JSON is error-prone and unsafe; users should not paste Gitea tokens into Claude/Gemini/Codex MCP configs.

Goal

Interactive setup/menu utility to create, edit, validate, and display safe launcher snippets for the canonical Gitea MCP profile config.

Behavior

  • Menu: list / add / edit / remove profiles; validate config; test auth; show authenticated user; generate thin launcher snippets (Claude/Gemini/Codex); check reviewer eligibility for a PR.
  • Auth by reference only: macOS keychain (security, service id like prgs-gitea-reviewer-token) or env var name (e.g. GITEA_TOKEN_PRGS_REVIEWER). Never echo/log/commit tokens; never write raw tokens into launcher configs.
  • Canonical file at ~/.config/gitea-tools/profiles.json: mkdir parents, atomic write, pretty JSON, preserve existing profiles.
  • Auth test + eligibility hit the API only on explicit selection; eligibility never approves/merges.
  • Backwards compatible: env-only mode unaffected; menu not required for MCP startup.

Delivery

Stacked on PR #30 (feat/json-runtime-profiles); merges after #30.

Refs #10, #19.

## Parent Roadmap #10. Depends on #19 / PR #30 (canonical runtime profiles). ## Problem Hand-editing the canonical profiles JSON is error-prone and unsafe; users should not paste Gitea tokens into Claude/Gemini/Codex MCP configs. ## Goal Interactive setup/menu utility to create, edit, validate, and display safe launcher snippets for the canonical Gitea MCP profile config. ## Behavior - Menu: list / add / edit / remove profiles; validate config; test auth; show authenticated user; generate thin launcher snippets (Claude/Gemini/Codex); check reviewer eligibility for a PR. - Auth by reference only: macOS keychain (`security`, service id like `prgs-gitea-reviewer-token`) or env var name (e.g. `GITEA_TOKEN_PRGS_REVIEWER`). Never echo/log/commit tokens; never write raw tokens into launcher configs. - Canonical file at `~/.config/gitea-tools/profiles.json`: mkdir parents, atomic write, pretty JSON, preserve existing profiles. - Auth test + eligibility hit the API only on explicit selection; eligibility never approves/merges. - Backwards compatible: env-only mode unaffected; menu not required for MCP startup. ## Delivery Stacked on PR #30 (`feat/json-runtime-profiles`); merges after #30. Refs #10, #19.
jcwalker3 added the status:in-progress label 2026-07-01 22:26:53 -05:00
sysadmin removed the status:in-progress label 2026-07-02 01:30:36 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
chore
documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 important
mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
read-only
Read-only, no mutation
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#31
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?