• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / cli / 26741249960
64%

Build:
DEFAULT BRANCH: develop
Ran 01 Jun 2026 07:30AM UTC
Jobs 1
Files 219
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

01 Jun 2026 07:28AM UTC coverage: 63.804% (+0.006%) from 63.798%
26741249960

push

github

web-flow
fix(cli): drop redundant identify from identity stitch (#5396)

## Problem

Both the Go CLI's `StitchLogin` and the TS CLI's `X-Gotrue-Id`
interception fire `$create_alias` AND `$identify(distinctID, nil)`
back-to-back on a user's first successful stitch. The `$identify`
carries no person properties, so `$create_alias` already owns the entire
device→user merge in the person graph. The Identify is pure event-volume
waste.

This is the follow-up to #5366. That PR gated stitching in ephemeral
environments (CI, Docker, npx) to stop the identify spike. This one
tightens the path that still runs — persistent developer laptops — by
dropping the redundant call.

We verified the redundancy empirically: of 638K `posthog-go` `$identify`
events on 2026-05-26, zero carried `$anon_distinct_id` linkage,
confirming the merge comes entirely from the alias.

## Changes

- Go: remove `s.analytics.Identify(distinctID, nil)` from `StitchLogin`
in `apps/cli-go/internal/telemetry/service.go`.
- TS: remove `analytics.identify(gotrueId)` from the stitch in
`apps/cli/src/legacy/auth/legacy-platform-api.layer.ts`. The TS
`identify()` may have set default person properties (`cli_version`,
`os`, `arch`); accepting that small loss since subsequent `cli_*`
capture events carry the same data as event properties.
- Tests updated on both surfaces to assert `Alias` fires and `Identify`
does not.

Kept the surfaces 1:1 so the Go/TS telemetry parity holds. `identify`
stays on the `Analytics` interface — the `login` command still uses it
for `cli_login_completed`, which is a separate path.

Halves the remaining persistent-laptop stitch volume (~15K/day →
~7K/day). No effect on the spike population already handled by #5366.

GROWTH-890

---------

Co-authored-by: Julien Goux <hi@jgoux.dev>

10053 of 15756 relevant lines covered (63.8%)

7.08 hits per line

Coverage Regressions

Lines Coverage ∆ File
9
84.28
0.94% internal/telemetry/service.go
Jobs
ID Job ID Ran Files Coverage
1 26741249960.1 01 Jun 2026 07:30AM UTC 219
63.8
GitHub Action Run
Source Files on build 26741249960
  • Tree
  • List 219
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #26741249960
  • 34c3ce95 on github
  • Prev Build on develop (#26698610056)
  • Next Build on develop (#26758692508)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc