Repository navigation
Describe the Lab 4 regression as a pull request and the generic fix automation - #13
Merged
Merged
Conversation
…ion fix it Lab 4 Step 4 now merges the regression branch into main and tags the release from main. Step 5 describes the Cursor automation "Sentry issue to fix PR": a webhook fed by a Sentry internal integration, the Sentry MCP as a tool, and a prompt that maps the project to the app, diffs the last two releases, and opens one pull request against main. The prompt sheet step number now matches the lab. Co-authored-by: Claude <[email protected]>
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
1 participant
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.
Docs only.
Lab 4 Step 4 ships the regression the way regressions ship: PR #12 merges
lab4-drop-prompt-cacheintomain, and the release is tagged frommain. The patch file stays for people working alone.Lab 4 Step 5 describes the Cursor automation "Sentry issue to fix PR". It is generic on purpose: a webhook fed by a Sentry internal integration, the Sentry MCP as a tool, and a prompt that maps the Sentry project to the app directory, diffs the issue's release against the previous one, makes the smallest fix, and opens one pull request against
main. Attendees can copy it into their own repos.The prompt sheet step number for the release comparison now matches the lab.
Created with Claude Code