|
@@ -1,7 +1,7 @@
|
|
|
# Repository Guidelines
|
|
# Repository Guidelines
|
|
|
|
|
|
|
|
## Project Structure & Module Organization
|
|
## Project Structure & Module Organization
|
|
|
-All scripts live at the repository root to be discoverable from the WSL `$PATH`. Wrapper utilities sit alongside their Windows counterparts: `win_edit`, `win_diff`, `win_python`, and `win_svn_dialog`. Shared Subversion helpers reside in `svn_interact/`, with `svn_git_init` symlinked for convenience. Keep new scripts self-contained at the top level or grouped in a subdirectory with a symlinked entry point when reuse is required.
|
|
|
|
|
|
|
+All scripts live at the repository root to be discoverable from the WSL `$PATH`. Wrapper utilities sit alongside their Windows counterparts: `win_edit`, `win_diff`, `vls_python`, and `win_svn_dialog`. Shared Subversion helpers reside in `svn_interact/`, with `svn_git_init` symlinked for convenience. Keep new scripts self-contained at the top level or grouped in a subdirectory with a symlinked entry point when reuse is required.
|
|
|
|
|
|
|
|
## Build, Test, and Development Commands
|
|
## Build, Test, and Development Commands
|
|
|
These Bash wrappers ship without a build step; prefer quick local smoke checks instead. Use `bash -n ./script_name` for syntax validation and `shellcheck ./script_name` to surface style or portability issues. When touching `svn_interact` helpers, run them against a staging checkout (`/mnt/d/...`) to confirm argument flow before pushing.
|
|
These Bash wrappers ship without a build step; prefer quick local smoke checks instead. Use `bash -n ./script_name` for syntax validation and `shellcheck ./script_name` to surface style or portability issues. When touching `svn_interact` helpers, run them against a staging checkout (`/mnt/d/...`) to confirm argument flow before pushing.
|