docs(seer): Clarify what makes a repo seer-enabled#16858
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
…ature is toggled on, not a connected repo Trying to be consistent across the pricing and product pages
ryan953
force-pushed
the
ryan953/seer-connected
branch
from
fa5b9c4 to
452001a
Compare
coolguyzone
approved these changes
Mar 10, 2026
Contributor
coolguyzone
left a comment
coolguyzone
left a comment
There was a problem hiding this comment.
Looks good, thanks for helping keep things clear and consistent 🤙
sfanahata
approved these changes
Mar 10, 2026
Contributor
sfanahata
left a comment
sfanahata
left a comment
There was a problem hiding this comment.
Suggested small word change just to use a different one than "enable" to define "enable", but nothing blocking. 🚢
Co-authored-by: Shannon Anahata <shannon.anahata@gmail.com>
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
3 participants
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.
Trying to be consistent across the pricing and product pages
DESCRIBE YOUR PR
I'm trying to be consistent across the pricing and product pages, and clarify what a
seer-connectedseer-enabled repo is.The affected pages are:
/pricing/quotas/manage-seer-budget//pricing//pricing/legacy-pricing//product/ai-in-sentry/seer/IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
EXTRA RESOURCES