Skip to content

chore: move setup/dev scripts into scripts/ directory - #74

Merged
GRACENOBLE merged 2 commits into
mainfrom
move-scripts-to-scripts-dir
Jul 17, 2026
Merged

chore: move setup/dev scripts into scripts/ directory#74
GRACENOBLE merged 2 commits into
mainfrom
move-scripts-to-scripts-dir

Conversation

@GRACENOBLE

@GRACENOBLE GRACENOBLE commented Jul 16, 2026

Copy link
Copy Markdown
Owner

Summary

  • Moved setup.sh, setup.ps1, dev.sh, dev.ps1 from the repo root into a new scripts/ directory
  • Fixed each script's self-location resolution (SCRIPT_DIR / $ScriptDir) to point one level up to the repo root, since they cd into backend/ and web/ relative to that path
  • Updated Makefile's setup and dev targets to call scripts/setup.{sh,ps1} and scripts/dev.{sh,ps1}
  • Updated README.md and CONTRIBUTING.md command references and the project structure tree

Test plan

  • Verified SCRIPT_DIR resolves to the repo root from scripts/ and correctly finds backend/ and web/
  • Grepped repo for any remaining root-level script references — none found outside scripts/ itself

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Improvements

    • Updated setup and development commands to use scripts from the scripts/ directory.
    • Improved path handling so setup and service startup work correctly from the relocated scripts.
    • Preserved separate macOS/Linux and Windows workflows for launching services.
  • Documentation

    • Updated the README and contributor instructions with the revised commands and project structure.

Consolidates setup.sh, setup.ps1, dev.sh, and dev.ps1 under a top-level
scripts/ directory instead of cluttering the repo root, and updates the
Makefile plus README/CONTRIBUTING references accordingly.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Setup and development scripts are referenced from the scripts/ directory across documentation and Makefile targets. The scripts now resolve the repository root before executing existing service startup, dependency installation, environment setup, and migration commands.

Changes

Scripts directory path migration

Layer / File(s) Summary
Update setup and development command paths
CONTRIBUTING.md, Makefile, README.md
Setup and development instructions, Makefile targets, and the documented project tree now use the scripts/ paths.
Resolve script paths from the repository root
scripts/dev.ps1, scripts/dev.sh, scripts/setup.ps1, scripts/setup.sh
Shell and PowerShell scripts derive the repository root for their existing relative path operations.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and accurately summarizes the main change: moving setup and dev scripts into the scripts directory.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch move-scripts-to-scripts-dir

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai 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.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@scripts/dev.ps1`:
- Line 5: Save scripts/dev.ps1 using UTF-8 encoding with a BOM, preserving its
existing contents and non-ASCII characters such as — and →.

In `@scripts/setup.ps1`:
- Line 6: Update the stale root-level command references in scripts/setup.ps1 at
lines 2, 116, and 170 to use .\scripts\setup.ps1 and .\scripts\dev.ps1 as
appropriate. Also update the prerequisite-failure rerun message in
scripts/setup.sh at line 102 to use ./scripts/setup.sh; no other behavior
changes are needed.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4700efaa-2022-4da3-9ab5-6efcf36123c3

📥 Commits

Reviewing files that changed from the base of the PR and between 7670934 and 3874b0d.

📒 Files selected for processing (7)
  • CONTRIBUTING.md
  • Makefile
  • README.md
  • scripts/dev.ps1
  • scripts/dev.sh
  • scripts/setup.ps1
  • scripts/setup.sh

Comment thread scripts/dev.ps1
Comment thread scripts/setup.ps1
- Save scripts/dev.ps1 as UTF-8 with BOM so Windows PowerShell
  correctly reads its non-ASCII characters (em dash, arrow)
- Update remaining stale root-level usage/rerun instructions in
  setup.sh, setup.ps1, dev.sh, and dev.ps1 to the new scripts/ path

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@GRACENOBLE
GRACENOBLE merged commit bdebf09 into main Jul 17, 2026
1 check passed
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.

1 participant