Update migration instructions for entire/sessions-legacy workflow#152
Merged
Update migration instructions for entire/sessions-legacy workflow#152
Conversation
- Source branch is now entire/sessions-legacy (renamed before migration) - Add BEFORE MIGRATION section with rename step - Update AFTER MIGRATION with remote rename and push steps - Update ROLLBACK instructions Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the migration script documentation to use a clearer branch naming workflow. Instead of migrating directly from entire/sessions, users are now instructed to first rename their existing entire/sessions branch to entire/sessions-legacy, which provides better clarity about which branch is the old format and serves as a safer backup during migration.
Changes:
- Updated all documentation references from
entire/sessionstoentire/sessions-legacyas the migration source - Added "BEFORE MIGRATION" section with explicit rename instruction
- Enhanced "AFTER MIGRATION" section with remote branch rename and cleanup steps
- Updated "ROLLBACK" instructions to account for the renamed legacy branch
gtrrz-victor
approved these changes
Feb 5, 2026
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
2 participants
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.
Summary
entire/sessions-legacyas source branchMigration Workflow
entire/sessionstoentire/sessions-legacyentire/sessionsto avoid conflictentire/sessions/v1to remoteentire/sessions-legacy🤖 Generated with Claude Code
Note
Low Risk
Comment/instruction-only updates plus a source-branch constant rename; no migration logic changes, but incorrect following of the new remote-rename steps could disrupt branches.
Overview
Updates
scripts/migrate-sessions.shto treatentire/sessions-legacy(renamed fromentire/sessions) as the source branch when migrating toentire/sessions/v1.Refreshes the script’s inline workflow docs by adding a Before migration local-rename step, revising After migration to include renaming/deleting the remote
entire/sessionsbranch to avoid conflicts, and updating rollback guidance accordingly.Written by Cursor Bugbot for commit 86a1d7b. This will update automatically on new commits. Configure here.