chore(preprod): add docs for how to configure size analysis processing #16180
+35
−0
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
docs/product/size-analysis/index.mdx
Outdated
|
|
||
| ## Configuring Size Analysis Uploads | ||
|
|
||
| By default, all Sentry accounts have 100 builds of Size Analysis / month. Below our options for controlling which builds will process for Size Analysis. |
Contributor
There was a problem hiding this comment.
Below are our options for controlling which builds will process for Size Analysis.
chromy
approved these changes
Jan 27, 2026
Contributor
chromy
left a comment
chromy
left a comment
There was a problem hiding this comment.
lgtm % Nico's comment, thanks!
|  | ||
|
|
||
| By default, Size Analysis processes for all uploaded builds. You can configure filters to only process builds for specific criteria, i.e. `git_head_ref: main`, `build_configuration_name: Release`, etc. Below is an example filter for a specific bundle (`com.emergetools.hackernews`) and branch (`main`). | ||
|
|
Contributor
There was a problem hiding this comment.
it could be a good idea to link directly to the hackernews repo too
Contributor
There was a problem hiding this comment.
Agreed, we should link the hackernews repo in the above section Uploading Select Builds
NicoHinderling
approved these changes
Jan 27, 2026
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.
add docs for size analysis settings / processing
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