ClickUp Continuous Integration

Overview

Keep ordinary pull-request checks deterministic and secretless while retaining a separately protected probe for provider-contract drift.

Prerequisites

• The repository's test runner, ClickUp transport boundary, and CI platform
• Sanitized fixtures for v2 and any selected v3 response shapes
• A protected non-production credential and strict request ceiling for the optional live lane

Tool Discipline

Use Read, Glob, and Grep to inspect the repository, adapters, configuration names, tests, and evidence. Use WebFetch only for current official ClickUp documentation. Use Write or Edit after confirming the target file, Workspace boundary, and requested mode.

Current Contract

• Pin the official v2 and v3 OpenAPI inputs separately; do not model v3 as a complete replacement.
• Offline tests cover authentication, plan denial, pagination, rate headers, webhook typing, and redaction.
• The live lane uses GET /api/v2/user or GET /api/v2/team; it does not create or update work.
• Fork code never receives ClickUp credentials.

Authentication

Use a personal token only for accountable individual/testing work or OAuth Authorization Code for a user-facing integration. Inject the token server-side through a governed secret reference, send it in Authorization, verify authorized Workspace IDs, and never print the token, OAuth client secret, or webhook secret.

Instructions

1. Inventory every endpoint, version, fixture, secret reference, and network-bearing test.
2. Generate or validate transport types against pinned official OpenAPI inputs.
3. Add fixtures for success, common OAuth errors, 429 responses, null webhook fields, and page boundaries.
4. Test redaction, retry eligibility, version routing, and workspace allow-list enforcement.
5. Place the bounded live probe behind a trusted event and protected environment.
6. Publish status, schema versions, request count, and redacted drift evidence.

Approval Boundaries

Do not expose credentials to fork code or let CI create tasks, webhooks, members, ACLs, or hierarchy objects without a separate environment approval and cleanup plan.

Output

Return offline coverage, pinned schema digests, live-lane eligibility/result, workspace boundary, request count, and any provider drift.

Error Handling

Examples

The example below is a redacted operator receipt; it contains no task text, member data, credential, or webhook secret.

offline=pass; v2_schema=pinned; v3_schema=pinned; live=skipped(untrusted-event); writes=0

Resources

• Skill-specific official documentation
• OpenAPI specifications
• Authentication
• Rate limits