docs(seer): Iterate on seer/autofix/code-review docs for clarity and consistency#16835
docs(seer): Iterate on seer/autofix/code-review docs for clarity and consistency#16835
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
ryan953
changed the title
ryan953
force-pushed
the
ryan953/seer-docs
branch
from
f119a18 to
d95ce94
Compare
ryan953
force-pushed
the
ryan953/seer-docs
branch
from
a10458d to
b0c6a03
Compare
ryan953
force-pushed
the
ryan953/seer-docs
branch
from
0088a88 to
4b8c08d
Compare
ryan953
force-pushed
the
ryan953/seer-docs
branch
from
6ab9a6d to
3cb6447
Compare
| 3. Connect projects to repositories in [Seer Project Settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/projects/). Seer will use the repositories connected to the project to perform Root Cause Analysis and Code Generation. | ||
|
|
||
| 3. Optionally enable [PR creation](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/repos/) and/or delegate to a [coding agent](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/projects/#coding-agents). |
There was a problem hiding this comment.
If I turn off PR creation, I'm not turning off code generation, right? It feels like the two of these things are conflated in the project a little bit.
There was a problem hiding this comment.
correct yes.
- Sentry overall has the option to disable AI features, including Seer branded features. “Show Generative AI Features”
- Seer overall has the option to disable code-generation.
- This prevents workflow steps that specifically output PRs from running. Chat interfaces, where you can convince the bot to output anything, have no restrictions (however you would need to copy+paste manually).
- Within the Autofix workflow there are steps: Triage, Summary, RCA, Solution, Create PR
- You can configure the Autofix workflow to do the Create PR step automatically, or not do that step.
If you want to take a stab at getting that kind of thing into the docs i'd appreciate the boost.
There was a problem hiding this comment.
Happy to help clean this up!
There was a problem hiding this comment.
This prevents workflow steps that specifically output PRs from running
Right now in the docs we say that anything "write a fix" and beyond won't run. Is that still correct? I can generate code using that button without choosing to then create a PR.
sfanahata
left a comment
sfanahata
left a comment
There was a problem hiding this comment.
Generally looks good, but I have questions about when we want to release this and how we're choosing to use these terms in the product and beyond. Will take this to the Seer channel for convo too.
Co-authored-by: Shannon Anahata <shannon.anahata@gmail.com>
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
|
|
||
| Seer's Issue Autofix flow follows a three step process: | ||
|
|
||
| 1. [Root Cause Analysis](#root-cause-analysis): Analyze the issue using Sentry's context and your codebases and determine the root cause | ||
| 2. [Solution Identification](#solution-identification): Identify a solution based on the analysis |
There was a problem hiding this comment.
We can update this later but in the new revision of Autofix that hasn't gone out to customers yet we're changing "Solution" to "Plan" to align with the terminology used by coding agents.
There was a problem hiding this comment.
Will add something in Linear to check back once we start rolling out v3
…nge to Autofix. Updated some wording. Brought in changes from Master.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
3 participants
DESCRIBE YOUR PR
Updates the names and language we use to describe Aufofix and Code Review which are part of the Seer addon.
Pages you should take a look at in the preview env:
/-> "Fix Bugs Faster with Seer" section/product/ai-in-sentry//product/ai-in-sentry/seer//product/ai-in-sentry/seer/issue-autofix//product/ai-in-sentry/seer/code-review/Here's a guide to help:
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