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

Add pagination and API failure-mode coverage #67

New Issue
Open
opened 2026-07-02 05:43:23 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-02 05:43:23 -05:00
Owner
Copy Link
Copy Source

Add focused tests for API pagination and failure modes. The code should handle multi-page Gitea responses and common network/API failures predictably.

Acceptance criteria

  • Tests cover endpoints returning more than one page.
  • Tests cover missing/empty pagination headers where applicable.
  • Tests cover connection timeout behavior.
  • Tests cover DNS/network failure behavior.
  • Tests cover 502/503 upstream failures.
  • Tests cover malformed Gitea error payloads.
  • Errors are returned clearly without exposing secrets.
  • Existing successful-path behavior remains unchanged.
Add focused tests for API pagination and failure modes. The code should handle multi-page Gitea responses and common network/API failures predictably. ## Acceptance criteria * Tests cover endpoints returning more than one page. * Tests cover missing/empty pagination headers where applicable. * Tests cover connection timeout behavior. * Tests cover DNS/network failure behavior. * Tests cover 502/503 upstream failures. * Tests cover malformed Gitea error payloads. * Errors are returned clearly without exposing secrets. * Existing successful-path behavior remains unchanged.
jcwalker3 added the testingreliability labels 2026-07-02 05:43:58 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
Architecture / structural design
 bug
chore
design
Design / investigation, no implementation
 documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
portability
Cross-platform / portability
 read-only
Read-only, no mutation
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 workflow
Cross-tool workflow
No Label reliability testing
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#67
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?