-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Update imgs and copy to reflect new ui #13792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
Bundle ReportChanges will increase total bundle size by 860.21kB (4.07%) ⬆️. This is within the configured threshold ✅ Detailed changes
ℹ️ *Bundle size includes cached data from a previous commit Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
|
bb0aec1
to
fed774f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Git Merge Conflict Markers in Documentation
Unresolved Git merge conflict markers (<<<<<<< HEAD
, =======
, >>>>>>> bb0aec11f
) were accidentally committed to docs/pricing/quotas/manage-event-stream-guide.mdx
. These markers will be visible to users and may cause markdown rendering issues, making the documentation unreadable.
docs/pricing/quotas/manage-event-stream-guide.mdx#L123-L128
sentry-docs/docs/pricing/quotas/manage-event-stream-guide.mdx
Lines 123 to 128 in fed774f
<<<<<<< HEAD | |
In **[Project] > Settings > SDK Setup > Client Keys (DSN)**, click "Configure", and you can create multiple DSN keys per project and assign different (or no) rate limits to each key. This will allow you to dynamically allocate keys (with varying thresholds) depending on release, environment, and so on. | |
======= | |
In **[Settings > Projects > [Project] > SDK Setup > Client Keys (DSN)**, click "Configure", and you can create multiple DSN keys per project and assign different (or no) rate limits to each key. This will allow you to dynamically allocate keys (with varying thresholds) depending on release, environment, and so on. | |
>>>>>>> bb0aec11f (Update imgs and copy to reflect new ui) |
Bug: Unresolved Merge Conflict in Documentation
Git merge conflict markers (<<<<<<< HEAD
, =======
, >>>>>>> bb0aec11f
) are present in the docs/pricing/quotas/manage-event-stream-guide.mdx
file. These markers were accidentally committed and will render as plain text, breaking the documentation's formatting and confusing users.
docs/pricing/quotas/manage-event-stream-guide.mdx#L139-L144
sentry-docs/docs/pricing/quotas/manage-event-stream-guide.mdx
Lines 139 to 144 in fed774f
<<<<<<< HEAD | |
1. Go **[Project] > Settings > SDK Setup > Client Keys (DSN)** and open the project DSN key configuration under by clicking "Configure". | |
======= | |
1. Go to **Settings > Projects > [Project] > SDK Setup > Client Keys (DSN)** and open the project DSN key configuration under by clicking "Configure". | |
>>>>>>> bb0aec11f (Update imgs and copy to reflect new ui) |
Was this report helpful? Give feedback by reacting with 👍 or 👎
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM ✋
DESCRIBE YOUR PR
Updating some outdated screenshots and directions, see https://sentry-docs-git-ui-stream-guide.sentry.dev/pricing/quotas/manage-event-stream-guide/ to preview
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:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES