Skip to content

feat: snap before next command#1

Open
somersby10ml wants to merge 2 commits intomainfrom
codex/prioritize-snap-before-next-command
Open

feat: snap before next command#1
somersby10ml wants to merge 2 commits intomainfrom
codex/prioritize-snap-before-next-command

Conversation

@somersby10ml
Copy link
Owner

Summary

  • snap current account automatically before running next
  • mention auto-snapshot in ccrotate next docs

Testing

  • pnpm exec vitest run

https://chatgpt.com/codex/tasks/task_e_6894711c8d648330961fa36ddfcdecd9

This comment was marked as outdated.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@somersby10ml somersby10ml requested a review from Copilot August 7, 2025 10:07
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds automatic snapshotting functionality to the next command, ensuring the current account is saved before switching to the next account. This prevents data loss when rotating between accounts.

  • Integrates automatic snapshot creation into the next command execution flow
  • Updates documentation to reflect the new auto-snapshot behavior

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
lib/commands/next.js Adds automatic snapshot creation before account rotation with error handling
README.md Updates command description to mention automatic account saving

// First, automatically save the current account (like snap --force)
try {
const snapCommand = new SnapCommand(this.ccrotate);
await snapCommand.execute(true); // force = true, no user interaction
Copy link

Copilot AI Aug 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The execute method is being called with a boolean parameter true, but this assumes the SnapCommand's execute method accepts a force parameter. Consider verifying that the SnapCommand API supports this parameter signature, or use a more explicit options object like { force: true } for better API clarity.

Suggested change
await snapCommand.execute(true); // force = true, no user interaction
await snapCommand.execute({ force: true }); // force = true, no user interaction

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant