AIT-481: no third-party vendor names in customer-facing copy - #14
Merged
Conversation
|
Warning Review limit reachedNext included review available in 27 minutes. View limit detailsLimit details: You’ve used the included review currently available. Your 91 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Comment |
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.
AIT-446 set the rule: customer-facing copy does not name third-party vendors we have no business recommending. That pass cut Railway and Render from the development-advice page but left three logging libraries two paragraphs above it, and the same pattern survived elsewhere.
Cut in this PR:
Kept on purpose: the CLI telemetry disclosure that names our own Sentry project (required transparency, not a recommendation), cloudflared references (our own tunnel), and the whatsapp-ai-agent template Vercel references (its actual deploy target).
https://linear.app/hookmyapp/issue/AIT-481/no-third-party-vendor-names-in-customer-facing-copy