Conversation
Add team schema/type and two new API functions needed for project
creation. Also adds TEAM_ENDPOINT_REGEX so /teams/{org}/... endpoints
route to the correct region.
Adds `sentry project create <name> <platform> [--team] [--json]`. Supports org/name syntax (like gh repo create owner/repo), auto-detects org from config/DSN, and auto-selects team when the org has exactly one. Fetches the DSN after creation so users can start sending events immediately. All error paths are actionable — wrong org lists your orgs, wrong team lists available teams, 409 links to the existing project.
Semver Impact of This PR🟡 Minor (new features) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨
Bug Fixes 🐛
Internal Changes 🔧
🤖 This preview updates automatically when you update the PR. |
When the API returns 400 for an invalid platform string, show the same helpful platform list instead of a raw JSON error body.
Replace the confusing 'Or: - Available platforms:' pattern with a cleaner 'Usage: ... Available platforms:' layout. Applies to both missing platform and invalid platform errors.
- tryGetPrimaryDsn() → api-client.ts (was duplicated in view + create) - resolveTeam() → resolve-team.ts (reusable for future team-dependent commands) - parseOrgPrefixedArg() → arg-parsing.ts (reusable org/name parsing) - writeKeyValue() for aligned key-value output in create.ts - project/view.ts now uses shared tryGetPrimaryDsn instead of local copy
Codecov Results 📊✅ Patch coverage is 93.35%. Project has 3606 uncovered lines. Files with missing lines (71)
Coverage diff@@ Coverage Diff @@
## main #PR +/-##
==========================================
+ Coverage 74.59% 75.07% +0.48%
==========================================
Files 115 117 +2
Lines 14107 14465 +358
Branches 0 0 —
==========================================
+ Hits 10523 10859 +336
- Misses 3584 3606 +22
- Partials 0 0 —Generated by Codecov Action |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
# Conflicts: # src/lib/api-client.ts
The /teams/{org}/{team}/projects/ endpoint returns 404 for both a bad
org and a bad team. Previously we always blamed the team, which was
misleading when --team was explicit and the org was auto-detected wrong.
Now on 404 we call listTeams(orgSlug) to check:
- If it succeeds → team is wrong, show available teams
- If it fails → org is wrong, show user's actual organizations
Only adds an API call on the error path, never on the happy path.
The view command hint on 409 used the raw name ('My Cool App') instead
of the expected slug ('my-cool-app'), pointing to a non-existent target.
handleCreateProject404 was treating any listTeams failure as proof that the org doesn't exist. Now it checks the status code: only 404 triggers 'Organization not found'. Other failures (403, 5xx, network) get a generic message that doesn't misdiagnose the root cause.
Same class of bug as the previous fix in handleCreateProject404: resolveTeam was routing all ApiErrors from listTeams into the 'org not found' path. Now only 404 triggers that diagnosis. Other failures (403, 5xx) get a generic message that doesn't misdiagnose the cause.
# Conflicts: # plugins/sentry-cli/skills/sentry-cli/SKILL.md # src/lib/api-client.ts # src/lib/arg-parsing.ts # src/types/sentry.ts
- Extract shared fetchOrgListHint() in resolve-team.ts to deduplicate
org-list fetching logic (used by both resolve-team and create 404 handler)
- Use Writer type instead of inline { write } in writeKeyValue
- Simplify Awaited<ReturnType<typeof listTeams>> to SentryTeam[]
- Add fragility comment to isPlatformError (relies on API message wording)
- Fix test import to use barrel (types/index.js)
When a project slug is already taken, Sentry silently appends a random suffix (e.g., 'test1' becomes 'test1-0g'). This was confusing because the user had no indication why the slug differed from the name. Now shows: Note: Slug 'test1-0g' was assigned because 'test1' is already taken.
BYK
left a comment
BYK
left a comment
There was a problem hiding this comment.
Love that you both try to infer team and org automatically while supporting org/proj --team <team> syntax too.
See my comments and decide whether you wanna merge as it is or not. My 2 major concerns are the refactor (I may merge that before you see this) and the error when we find more than 1 team.
| * parseOrgPrefixedArg("acme/my-app", "Project name", "sentry project create <org>/<name>") | ||
| * // { org: "acme", name: "my-app" } | ||
| */ | ||
| export function parseOrgPrefixedArg( |
There was a problem hiding this comment.
I'm doing a massive refactor which may make this part obsolete.
There was a problem hiding this comment.
finally looked through the current infra after merging main, parseOrgProjectArg and dispatchOrgScopedList are for list/query commands. parseOrgPrefixedArg parses a new resource name, not an existing slug, and resolveTeam handles team auto-selection for write operations.
So i don't think they have an equivalent in your changes, maybe we could consolidate later with more create commands?
| * @returns Team slug to use | ||
| * @throws {ContextError} When team cannot be resolved | ||
| */ | ||
| export async function resolveTeam( |
Previously, project create errored whenever an org had 2+ teams, requiring --team in every non-trivial org. Now filters teams by isMember and auto-selects when the user belongs to exactly one team. When multiple member teams exist, only those are shown in the error (not all org teams). Falls back to the full list when isMember data is unavailable (self-hosted, old API).
…ists handleCreateProject404 now checks if the teamSlug is actually present in the returned teams list before claiming it's not found. When the team exists (e.g., auto-selected by resolveTeam), the error correctly reports a permission issue instead of the contradictory message.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| }; | ||
|
|
||
| /** Common Sentry platform strings, shown when platform arg is missing or invalid */ | ||
| const PLATFORMS = [ |
There was a problem hiding this comment.
This list is too narrow. We should at least be using https://github.com/getsentry/sentry/blob/411b4c5754e608c06754a3695a2630a23e6a6851/src/sentry/models/project.py#L64-L173
But ideally we fetch it at runtime from https://release-registry.services.sentry.io/sdks
There was a problem hiding this comment.
my thinking here was to show just a small list of the most used/popular ones If we show the 140, that would be way harder to read and fills all the terminal screen
| /** | ||
| * Convert a project name to its expected Sentry slug. | ||
| * Sentry slugs are lowercase, with non-alphanumeric runs replaced by hyphens. | ||
| * | ||
| * @example slugify("My Cool App") // "my-cool-app" | ||
| * @example slugify("my-app") // "my-app" | ||
| */ |
There was a problem hiding this comment.
Do we have this logic coded somewhere in the Sentry app? We should and if we do, this comment should refer to that specific location.
| "Usage:\n" + | ||
| ` sentry project create ${nameArg} <platform>\n\n` + | ||
| `Available platforms:\n\n${list}\n\n` + | ||
| "Full list: https://docs.sentry.io/platforms/" |
There was a problem hiding this comment.
See my earlier comment: we should list the ones from the release regists.
| throw new CliError( | ||
| `No teams found in ${orgSlug}.\n\n` + | ||
| "Create a team first, then try again." | ||
| ); |
There was a problem hiding this comment.
Can we offer creating a new, default team on the fly? Or actually "just do it"?
| * Write key-value pairs with aligned columns. | ||
| * Used for human-readable output after resource creation. | ||
| */ | ||
| function writeKeyValue( |
There was a problem hiding this comment.
This should be a shared utility across all commands
| fullDescription: | ||
| "Create a new Sentry project in an organization.\n\n" + | ||
| "The name supports org/name syntax to specify the organization explicitly.\n" + | ||
| "If omitted, the org is auto-detected from config defaults or DSN.\n\n" + |
There was a problem hiding this comment.
It's a bit confusing to me to detect anything form the DSN under this context as if we are creating a new project, that implies we don't typically have a DSN around?
| if (!resolved) { | ||
| throw new ContextError("Organization", USAGE_HINT, [ | ||
| `Include org in name: ${USAGE_HINT}`, | ||
| "Set a default: sentry org view <org>", |
There was a problem hiding this comment.
This is not how we set a default org. In fact we don't have the notion of a default org but I like it. Good follow up PR.
src/lib/api-client.ts
Outdated
| const regionUrl = await resolveOrgRegion(orgSlug); | ||
| const { data } = await apiRequestToRegion<SentryProject>( | ||
| regionUrl, | ||
| `/teams/${orgSlug}/${teamSlug}/projects/`, |
There was a problem hiding this comment.
Is the reason to not use @sentry/api things because they are not region-aware? If that's the case I think we should add the region-aware version to that package @MathurAditya724
| } | ||
|
|
||
| /** Parsed result from an `org/name` positional argument */ | ||
| export type ParsedOrgPrefixed = { |
There was a problem hiding this comment.
I'm 100% sure we have something better than this introduced in https://github.com/getsentry/cli/pull/262/changes (or already existing)
3 participants
Summary
Adds
sentry project create <name> <platform>— the first write command in the CLI. Followsgh repo createconventions with org/name syntax, auto-detection of org and team, and actionable errors at every step.Changes
SentryTeamZod schema and typelistTeams()andcreateProject()API functions with region-aware routing (TEAM_ENDPOINT_REGEX)project createcommand with two required positionals,--team/-tflag, and--jsonoutputTest Plan
bun test test/commands/project/create.test.ts— 19 pass, 0 failbun run typecheck— cleanbun run lint— clean