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>
web-tracker-domain
Modelo del tracker en el cliente.
- Import:
@task-stream/web/tracker/domain - Capa:
domain· Tags:scope:web-tracker,type:domain
Contenido
- Modelos (
Project,IssueSummary,Issue,Release…), enums e inputs. - Configuración por proyecto (
ProjectSettings,StatusCategory) yWorkflow: nombres, colores, iconos, categorías, transiciones permitidas y estados que piden motivo, con un nombre legible para ids que ya no están configurados. - Estadísticas (
ProjectAnalytics,ReleaseBurnup). - Puertos:
ProjectsGateway,IssuesGateway,CommentsGateway,ReleasesGateway,ActivityGateway,UsersGateway,TrackerRealtimeGateway.
Comandos
npx nx lint web-tracker-domain
npx nx test web-tracker-domain # Jest
Reglas de dependencia entre capas: Arquitectura.