personal-projects/gitea-mcp-remote
1
0
Fork 0
generated from personal-projects/leo-claude-mktplace
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

[Sprint 02] refactor: Remove incorrect standalone MCP implementation #9

New Issue
Closed
opened 2026-02-03 21:00:15 +00:00 by lmiranda · 0 comments
lmiranda commented 2026-02-03 21:00:15 +00:00
Owner
Copy Link

Summary

Delete the current standalone MCP server implementation, as it duplicates tool logic that should be imported from the marketplace package.

Tasks

  • Delete src/gitea_mcp/ directory entirely
  • Delete tests/ directory entirely
  • Keep pyproject.toml for rewriting in next issue
  • Keep .env, .gitignore, README.md for updating later
  • Verify clean state with git status

Acceptance Criteria

  • src/gitea_mcp/ does not exist
  • tests/ does not exist
  • Repository is in clean state ready for correct structure
  • No tool logic remains in this repository

Context

This repository was incorrectly structured as a standalone MCP server. It should be a thin deployment wrapper that imports tools from the gitea-mcp-server marketplace package.

References:

  • Corrective Rebuild specification (Sprint 02)
  • Step 1 of 14-step rebuild plan

Size: S (1-2 hours)

## Summary Delete the current standalone MCP server implementation, as it duplicates tool logic that should be imported from the marketplace package. ## Tasks - [ ] Delete `src/gitea_mcp/` directory entirely - [ ] Delete `tests/` directory entirely - [ ] Keep `pyproject.toml` for rewriting in next issue - [ ] Keep `.env`, `.gitignore`, `README.md` for updating later - [ ] Verify clean state with `git status` ## Acceptance Criteria - `src/gitea_mcp/` does not exist - `tests/` does not exist - Repository is in clean state ready for correct structure - No tool logic remains in this repository ## Context This repository was incorrectly structured as a standalone MCP server. It should be a thin deployment wrapper that imports tools from the `gitea-mcp-server` marketplace package. **References:** - Corrective Rebuild specification (Sprint 02) - Step 1 of 14-step rebuild plan **Size:** S (1-2 hours)
lmiranda added this to the Sprint 02: Corrective Rebuild milestone 2026-02-03 21:00:15 +00:00
lmiranda added the Type/SetupComponent/BackendPriority/HighSize/S labels 2026-02-03 21:00:15 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend/server-side code
 Component/Backend
Backend service code and business logic
 Component/Core
Core application logic and architecture
 Component/Database
Database schemas, migrations, queries
 Component/Dependencies
Package dependencies and requirements
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docker
Docker and containerization
 Component/Docs
Documentation and guides
 Component/Documentation
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Integration
Integration and end-to-end testing
 Component/Testing
Test infrastructure and frameworks
 Priority/Critical
Critical priority - blocks other work
 Priority/High
High priority items
 Priority/Medium
Medium priority items
 Size/L
Large task (4-8 hours)
 Size/M
Medium task (2-4 hours)
 Size/S
Small task (1-2 hours)
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
 Type/Build
Build system and dependencies
 Type/Documentation
Documentation updates
 Type/Feature
New feature implementation
 Type/Refactor
Code refactoring and restructuring
 Type/Setup
Initial project setup tasks
 Type/Test
Testing and quality assurance
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label Component/Backend Priority/High Size/S Type/Setup
Milestone
No items
No Milestone Sprint 02: Corrective Rebuild
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/gitea-mcp-remote#9
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?