A project keeps a list of repositories (api, web, admin…), each with its own secret, instead of a single webhook secret. They all call the same URL; the secret that verifies the signature tells which one it was, and every commit, branch or pull request is linked with its repository's name (shown on the ticket and in the MCP). Rotating or removing one leaves the others alone, and what it linked stays. A project that had turned the single webhook on keeps its secret, as a repository named "principal". API: the enable/disable endpoints and mutations give way to adding a repository, rotating its secret and removing it (REST and GraphQL). The web settings card lists the repositories. Docs, Word and PDF updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
api-tracker-presenters
API GraphQL y REST (OpenAPI) del tracker.
- Import:
@task-stream/api/tracker/presenters - Capa:
presenters· Tags:scope:api-tracker,type:presenters
Contenido
- Resolvers
ProjectResolver,IssueResolver,CommentResolver,ReleaseResolverySubscriptionResolver; solo llaman a services. - Tipos, inputs (con
class-validator) y enums de GraphQL (code-first). http/: controladores RESTProjectsController,IssuesController,CommentsController,ReleasesController(mismos services), DTOs con@nestjs/swaggeryRefs(proyectos y tickets por id o clave; añade a cada ticket sus transiciones permitidas según el workflow de su proyecto).ExploreController(GET /api/explore/projects, sin token). Las lecturas usan@OptionalAuth()yviewerOf(me)(null = anónimo) para servir proyectos públicos sin sesión.common/settings.ts: configuración del proyecto con las transiciones como lista (lo que viaja por GraphQL y REST).
Operaciones disponibles: GraphQL y REST.
Comandos
npx nx lint api-tracker-presenters
npx nx test api-tracker-presenters # Jest
Reglas de dependencia entre capas: Arquitectura.