Dashboard › cli › Distillation
02a39a04-ff44-46ff-9d13-ac477e8a154b["lore_tm_v1_W94EGsyKDN38xQIFqsq79yoWTF85TgZFPExsy3zk5VQ","lore_tm_v1_m46OKewBAjrCHN8UlNbAOlgC0dIY1zoCX28QAz7sLxs","lore_tm_v1_GSiO1hlEZi3r_s79Y3kepb07eULEke1ooNgIMW6-_Ao","lore_tm_v1_mgPMO1nex3dYRGAZ-oH8otOLAEfq02MzO5AYdeHMNqE","lore_tm_v1_ezgVgWEBhTOijm6y0vh02772pIsdAqFJLijnc9Kz968","lore_tm_v1_KRi2j-I13CA6GT9bYTpaDn7u3W4cLbY-L_dOzynEWus","lore_tm_v1_FphfgUM-GJ6NEy8Jnt_7K2lfx-PIf-nKZP4BDsvfSlc","lore_tm_v1_ETn47Ac3yzpA-qHeHvJCl0tjtiDk-OyZX4a3JvC3_mE"]
--into always designates an issue that participates in the merge as the preferred parent; it is appended to the positional issue list before resolution.--into must resolve to one of the provided issues or a ValidationError is raised.packages/cli/src/commands/schema.ts defines unauthenticated schemaCommand for browsing an in-memory Sentry API schema; sentry schema returns resource summaries, sentry schema <resource> [operation] calls resolveResourceQuery(resource, operation), and glob patterns are supported by that resolver.schemaCommand supports --all for getAllEndpoints() and --search/-q for searchEndpoints(flags.search); --search takes priority over --all and positional arguments.schemaCommand --search query with no matches throws OutputError({ kind: "endpoints", endpoints: [] }); successful endpoint results use { kind: "endpoints", endpoints }, while the no-argument resource overview uses { kind: "resources", resources }.packages/cli/src/commands/monitor/run.ts defines sentry monitor run <monitor-slug> -- <command>, wrapping an arbitrary child command with an in_progress cron-monitor check-in followed by an ok or error check-in containing duration.monitor run resolves its DSN in this order: --dsn, SENTRY_DSN, then project-source auto-detection through detectDsn(cwd); no Bearer-token login is required. Missing DSN raises ConfigError, and makeDsn() failure raises ValidationError(\Invalid DSN: ${dsn}`, "dsn")`.sendCheckInSafely() logs and swallows send failures, races sendEnvelopeRequest() against CHECKIN_SEND_TIMEOUT_MS = 30_000, and drains a later rejected send promise to prevent an unhandled rejection.monitor run requires both a monitor slug and child command, using usage hint sentry monitor run <monitor-slug> -- <command>; the -- separator is recommended when the child has flags but optional otherwise, and a leading passed-through -- is stripped defensively.monitor run flags include --dsn; --environment/-e defaulting to production; --schedule/-s; and positive-integer --check-in-margin, --max-runtime, --failure-issue-threshold, and --recovery-threshold, plus --timezone. Monitor-configuration dependent flags require --schedule; integer values must be at least 1.monitor run --schedule supplies an upsert monitor configuration only on the opening in_progress check-in; the final check-in omits configuration and uses the same checkInId generated by uuid4().SENTRY_MONITOR_SLUG=<monitorSlug>, and has SIGINT and SIGTERM forwarded through persistent process.on() handlers so repeated signals reach the child without prematurely killing the parent and skipping the closing check-in.monitor run preserves child exit behavior: normal exit codes are retained; signal exits map to Unix 128 + signal number such as 130 for SIGINT, 137 for SIGKILL, and 143 for SIGTERM; an indeterminate close maps to 1.monitor run records the spawn error, sends a final error check-in with exit code 1, then throws CliError(\Failed to start "${cmd}": ${spawnError.message}`, 1); other nonzero exits produce CliError(`Process exited with code ${exitCode}`, exitCode)`.monitor run duration is calculated as (Date.now() - startedAt) / 1000; status is ok only for exit code 0, otherwise error.packages/cli/src/commands/project/create.ts defines sentry project create [<org>/]<name>:<platform>... for creating one or more projects; every platform must always be attached with :, with no space-separated form whether or not an organization is explicit, and project names cannot contain whitespace.project create specifications are separate name:platform arguments, all must resolve to one organization, and organization resolution precedence is positional prefix, environment variables, configuration defaults, then DSN auto-detection.project create normalizes platform identifiers containing dots by replacing every . with - and logging a warning, because SDK-guide notation such as javascript.nextjs differs from valid platform identifiers such as javascript-nextjs.sentry project create <name>:<platform>, suggestions from suggestPlatform(), a grid of COMMON_PLATFORMS, and directions to run sentry platform list.project create disambiguates a project-creation 404 by calling listTeams(orgSlug): if the team exists, it reports likely permission rejection; if other teams exist, it raises ResolutionError listing available team slugs; if the organization has no teams, it tells the user to create one; and if listTeams itself returns 404, it delegates to buildOrgNotFoundError().resolveDryRunTeam() mirrors the real project-creation fallback for users lacking team:read, but a project create --dry-run preview never actually creates the team; it uses a placeholder/pinned team slug so preview and real execution agree.packages/cli/src/commands/cli/feedback.ts defines unauthenticated sentry cli feedback; all positional arguments are joined with spaces and trimmed into one feedback message.sentry cli feedback receives no message, non-interactive stdin causes ValidationError("Please provide a feedback message."); interactive stdin prompts Enter your feedback message: with placeholder e.g. I love this tool!, and an empty response raises the same error.sentry cli feedback requires enabled telemetry; when Sentry.isEnabled() is false it throws ConfigError("Feedback not sent: telemetry is disabled.", "Unset SENTRY_CLI_NO_TELEMETRY to enable feedback.").getUserInfo() from ../../lib/db/user.js, calls Sentry.captureFeedback({ message, email: user?.email, name: user?.name ?? user?.username }), then waits for Sentry.flush(3000) and returns structured { sent, message }.