Skip to content

CODAP-1118: plugin undo/redo analysis document #2388

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.

Sign up for GitHub

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

Open
kswenson wants to merge 7 commits into
base: main
Choose a base branch
from
+377 −2
Open

CODAP-1118: plugin undo/redo analysis document #2388

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
8189e95
Add plugin undo/redo analysis document
kswenson Feb 13, 2026
8b6da57
Require branch name approval before creation
kswenson Feb 13, 2026
bd53818
Distinguish draft vs non-draft PR creation
kswenson Feb 13, 2026
28da881
Update plugin undo/redo analysis with revised conclusions
kswenson Feb 23, 2026
1b4f296
Address interleaving of user-triggered CODAP undo with plugin undo
kswenson Feb 23, 2026
71848d7
Revise analysis: shared-stack interleaving is chronologically correct
kswenson Feb 23, 2026
a6c1e3c
Verify withCustomUndoRedo supports pure side-effect undo entries
kswenson Feb 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,21 +27,24 @@ When the user says "Let's start work on CODAP-XXX" (or similar):
- Example: `CODAP-1027-inbounds-url-param`
- Use lowercase kebab-case for the description
- Keep it concise but descriptive
- **Always propose the branch name and get user approval before creating it**

3. **Update Jira status**: Transition the story to "In Progress"

### Creating a Pull Request

When the work is ready for initial CI validation:

1. **Create a draft PR**:
1. **Create a PR**:
- Title format: `{JIRA-ID}: {description}` (e.g., `CODAP-1027: add inbounds URL parameter`)
- Description should include:
- Summary of the changes
- Reference to the Jira story (e.g., `Fixes CODAP-1027` or link to the story) so Jira links it automatically
- Apply the `v3` label
- **For PRs with code changes**: Create as a draft PR. Mark as "Ready for Review" only after CI passes.
- **For docs-only PRs** (no code changes): Create as a regular (non-draft) PR — no need for CI validation.

2. **Initial CI validation**:
2. **Initial CI validation** (code PRs only):
- CI runs automatically on PRs (lint, build, limited Cypress tests)
- Review CI results and fix any issues

Expand Down
Loading