Repository navigation
Tag s1 login sign-ups with utm_source, release 2.1.1 - #14
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DuYf7uK9RY4Z3dfE6oxSaS
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
s1 loginnow addsutm_source=search1api-clito the browser authorization URL. The sign-in page records that value as the signup source, the same way Magpie 0.1.1 sendsutm_source=magpie. Until now, CLI signups were recorded only aslocalhost, so they couldn't be told apart from other desktop OAuth clients.src/auth.ts: adds theutm_sourceparameter to the authorization URL.tests/oauth-e2e.test.mjs: asserts the parameter is sent.npm testpasses (30/30, including the OAuth e2e test).Generated by Claude Code