Skip to content

chore: add transfer test script and document debugging scripts#139

Merged
joshua-quek-sonarsource merged 1 commit into
mainfrom
chore/add-transfer-test-script
Apr 29, 2026
Merged

chore: add transfer test script and document debugging scripts#139
joshua-quek-sonarsource merged 1 commit into
mainfrom
chore/add-transfer-test-script

Conversation

@joshua-quek-sonarsource

@joshua-quek-sonarsource joshua-quek-sonarsource commented Apr 29, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add .debugging/test-transfer.sh for quick local testing of the transfer command
  • Gitignore transfer-config.json (credentials) and *.lock files
  • Document all .debugging/ scripts in docs/local-development.md

Test plan

  • Verify transfer-config.json is not tracked by git
  • Run .debugging/test-transfer.sh with a valid config.json to confirm it invokes the transfer command correctly

🤖 Generated with Claude Code


Note

Cursor Bugbot is generating a summary for commit be3ec48. Configure here.

Add test-transfer.sh for quick local testing of the transfer command,
gitignore transfer-config.json and *.lock files, and document all
.debugging/ scripts in local-development.md.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@joshua-quek-sonarsource
joshua-quek-sonarsource merged commit 88296de into main Apr 29, 2026
1 of 2 checks passed
@sonar-review-alpha

sonar-review-alpha Bot commented Apr 29, 2026

Copy link
Copy Markdown

Summary

This PR adds a new debugging test script for the transfer command and improves documentation for local development. It includes:

  • New script: .debugging/test-transfer.sh follows the existing pattern of test-migrate.sh and test-verify.sh, enabling quick local testing with a config file
  • Gitignore updates: Adds transfer-config.json (credentials) and *.lock files to prevent accidental commits
  • Documentation: Creates a new "Debugging Scripts" section in docs/local-development.md that documents all scripts in .debugging/ with a handy reference table, clarifying which config file each script uses and their purpose

What reviewers should know

Review focus:

  • The new test script is minimal but consistent with existing debugging scripts
  • The gitignore additions mirror the existing pattern (migrate-config.json was already ignored)
  • Documentation is well-organized and includes a clear caveat about why config files are gitignored (credentials)

What to verify:

  • Confirm the binary path in test-transfer.sh (./dist/bin/cloudvoyager-macos-arm64) matches your platform expectations
  • Check that *.lock files are the right thing to ignore (likely dependency lock files from your build/package manager)

  • Generate Walkthrough
  • Generate Diagram

🗣️ Give feedback

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit be3ec48. Configure here.

@@ -0,0 +1,3 @@
#!/bin/bash

./dist/bin/cloudvoyager-macos-arm64 transfer -c config.json --force-restart

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Script uses wrong config filename, contradicts docs

Medium Severity

The test-transfer.sh script passes -c config.json but the documentation, the .gitignore entry, and the naming convention from sibling scripts (test-migrate.sh uses migrate-config.json) all indicate it needs to use transfer-config.json. A developer following the docs would create transfer-config.json but the script would never read it, instead picking up a different (or nonexistent) config.json.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit be3ec48. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants