- Removed duplicate 'custom path' example from both bash and PowerShell scripts
- Example 2 already demonstrates custom path usage with Setup Home
- Updated README.md to match the streamlined 3-example format
- All examples now provide distinct, non-overlapping use cases
- Marked -to as (recommended)
- Replaced default-org example with explicit org + custom path example
- Keeps examples consistent across Bash and PowerShell and with environments without a default org
🔄 PowerShell Option Consistency - Phase 1 Complete:
✅ Updated Scripts:
- sf-deploy.ps1: -to, -sr, -dr, -ts, -hp (matches Bash)
- sf-dry-run.ps1: -to, -sr, -dr, -ts, -hp (matches Bash)
- sf-web-open.ps1: -to, -pt, -ur, -hp (matches Bash)
- sf-check.ps1: -vb, -hp (matches Bash)
- sf-org-create.ps1: -al, -dd, -df, -st, -tp, -hp (matches Bash)
🎯 Consistency Achieved:
- All parameter names now match their Bash counterparts exactly
- Help text updated with descriptive option names
- Examples updated to show new two-character options
- All validation logic updated to use new parameter names
🚀 Cross-Platform Alignment:
- PowerShell and Bash scripts now have identical option schemes
- Users get consistent experience across platforms
- No more confusion between single-char and two-char options
Remaining: 7 more PowerShell scripts to update for full consistency.
