MokoConsulting/MokoGitea-Fork
1
0
Fork 0
Code Issues 160 Pull Requests Releases 96 Wiki Activity

test: metadata API and settings page #685

New Issue
Open
opened 2026-06-21 23:04:34 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-21 23:04:34 +00:00
Owner
Copy Link
Copy Source

Parent: #683

Metadata Tests

Public API (#676)

  • curl https://git.mokoconsulting.tech/api/v1/repos/MokoConsulting/MokoCLI/metadata — returns JSON without auth
  • curl https://git.mokoconsulting.tech/api/v1/repos/MokoConsulting/MokoCLI/manifest — backward compat works
  • Private repo metadata returns 404 for unauthenticated requests
  • PUT still requires token + admin auth (try without → 403)

Settings Page (Version field fix)

  • Visit any repo → Settings → Metadata → page loads without 500 error
  • Version input field is gone (was causing the crash)
  • All other metadata fields (name, org, platform, license) editable
  • Save metadata → changes persist
Parent: #683 ## Metadata Tests ### Public API (#676) - [ ] `curl https://git.mokoconsulting.tech/api/v1/repos/MokoConsulting/MokoCLI/metadata` — returns JSON without auth - [ ] `curl https://git.mokoconsulting.tech/api/v1/repos/MokoConsulting/MokoCLI/manifest` — backward compat works - [ ] Private repo metadata returns 404 for unauthenticated requests - [ ] PUT still requires token + admin auth (try without → 403) ### Settings Page (Version field fix) - [ ] Visit any repo → Settings → Metadata → page loads without 500 error - [ ] Version input field is gone (was causing the crash) - [ ] All other metadata fields (name, org, platform, license) editable - [ ] Save metadata → changes persist
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 feature: wiki
Wiki system enhancements
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
No labels
Priority Medium
Type Feature
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-Fork#685
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?