[Gap Analysis] Missing CRUD Operations for Issues and Pull Requests in gitea/dev.py #3
Reference in New Issue
Block a user
No description provided.
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?
Summary
The
gitea/dev.pytool provides partial Gitea API coverage but is missing critical CRUD operations for Issues and Pull Requests. This limits autonomous LLM workflows that require reading, updating, or commenting on artifacts.Current Coverage Assessment
✅ Implemented Functions (17 total)
list_repos,get_repolist_files,get_file,create_file,update_file,delete_filelist_branches,create_branchlist_commits,get_commitlist_issues,create_issuelist_pull_requests,create_pull_requestget_project_context❌ Missing Functions (16 total)
Issues (8 missing)
Pull Requests (8 missing)
Gap Matrix
Impact on LLM Autonomy
Blocked Workflows
Issue Triage Loop
PR Review Automation
Stale Issue Management
Gitea API Endpoints Required
GET /repos/{owner}/{repo}/issues/{index}PATCH /repos/{owner}/{repo}/issues/{index}DELETE /repos/{owner}/{repo}/issues/{index}GET /repos/{owner}/{repo}/issues/{index}/commentsPOST /repos/{owner}/{repo}/issues/{index}/commentsGET /repos/{owner}/{repo}/pulls/{index}PATCH /repos/{owner}/{repo}/pulls/{index}POST /repos/{owner}/{repo}/pulls/{index}/mergeGET /repos/{owner}/{repo}/pulls/{index}/reviewsRecommended Priority
get_issue,get_pull_request- Block reading individual itemsupdate_issue,update_pull_request- Block editing artifactscreate_issue_comment,create_pull_request_comment- Block feedback loopsclose_issue,reopen_issue- State managementlist_issue_comments,list_pull_request_comments- Read-only contextReference Implementation Pattern
Next Steps
Add the missing functions following the established patterns in
gitea/dev.py:_resolve_repo,_headers,_format_errorhelpers