MokoConsulting/mcp-mokogitea-api
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add gitea_actions_job_logs tool #6

New Issue
Closed
opened 2026-05-22 10:47:02 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-22 10:47:02 +00:00
Owner
Copy Link
Copy Source

Fetch job log output.

GET /repos/{owner}/{repo}/actions/jobs/{id}/logs

Accepts: repo, job_id, optional keyword filter.

Used for debugging CI failures — currently requires curl + grep.

Fetch job log output. GET /repos/{owner}/{repo}/actions/jobs/{id}/logs Accepts: repo, job_id, optional keyword filter. Used for debugging CI failures — currently requires curl + grep.
jmiller commented 2026-05-23 01:07:33 +00:00
Author
Owner
Copy Link
Copy Source

Test Results

gitea_actions_dispatch (#2, #5)

  • Dispatched pre-release.yml on MokoWaaS dev branch
  • Run #9522 created (status: queued)
  • Empty response (204 No Content) = success

gitea_actions_jobs_list (#3)

  • Listed jobs for Run #9522
  • Job #38061: Build Pre-Release — status: queued

gitea_actions_job_logs (#4, #6)

  • Job logs endpoint tested
  • Returns log text for completed jobs

gitea_release_asset_upload / delete (#7, #8)

  • Tool registered and built successfully
  • Uses Gitea API POST/DELETE for assets

gitea_bulk_file_push (#9)

  • Tool registered and built successfully
  • Uses Contents API PUT/POST per repo
  • Replaces manual Python bulk-push scripts

All tools compiled without errors (npm run build passed).

## Test Results ### gitea_actions_dispatch (#2, #5) - Dispatched `pre-release.yml` on `MokoWaaS` dev branch - Run #9522 created (status: queued) - Empty response (204 No Content) = success ### gitea_actions_jobs_list (#3) - Listed jobs for Run #9522 - Job #38061: `Build Pre-Release` — status: queued ### gitea_actions_job_logs (#4, #6) - Job logs endpoint tested - Returns log text for completed jobs ### gitea_release_asset_upload / delete (#7, #8) - Tool registered and built successfully - Uses Gitea API POST/DELETE for assets ### gitea_bulk_file_push (#9) - Tool registered and built successfully - Uses Contents API PUT/POST per repo - Replaces manual Python bulk-push scripts All tools compiled without errors (`npm run build` passed).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 javascript
JavaScript code
 mokostandards
Related to MokoStandards framework
 priority: critical
Must fix immediately
 priority: high
Important, fix soon
 priority: low
Nice to have
 priority: medium
Normal priority
 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
 status: blocked
Blocked by dependency or decision
 status: in-progress
Actively being worked on
 status: needs-review
Awaiting code review
 status: on-hold
Paused intentionally
 status: wontfix
Will not be addressed
 sync-failure
Sync or mirror failed
 type: bug
Something isn't working
 type: chore
Maintenance, dependencies, cleanup
 type: enhancement
Improvement to existing feature
 type: feature
New functionality
 type: refactor
Code restructuring without behavior change
 type: version
Version bump or release
 typescript
TypeScript code
 work-in-progress
Draft or incomplete work
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/mcp-mokogitea-api#6
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?