You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,9 @@ pip install -e ".[dev]"
28
28
29
29
## Quick Start
30
30
31
-
1. Create a `.env.example` template in your project root (and optionally in subdirectories):
31
+
**Note**: Sprout works in any git repository. `.env.example` files are optional - if you don't have them, sprout will simply create worktrees without `.env` generation.
32
+
33
+
1. (Optional) Create a `.env.example` template in your project root (and optionally in subdirectories) for automatic `.env` generation:
32
34
```env
33
35
# API Configuration
34
36
API_KEY={{ API_KEY }}
@@ -58,9 +60,13 @@ repo/
58
60
cd$(sprout create feature-branch --path)
59
61
```
60
62
63
+
**What happens when you run `sprout create`:**
64
+
- If `.env.example` files exist: Sprout will generate corresponding `.env` files with populated variables and unique port assignments
65
+
- If no `.env.example` files exist: Sprout will show a warning and create the worktree without `.env` generation
66
+
61
67
This single command:
62
68
- Creates a new git worktree for `feature-branch`
63
-
- Generates a `.env`file from your template
69
+
- Generates `.env`files from your templates (if `.env.example` files exist)
64
70
- Outputs the path to the new environment
65
71
- Changes to that directory when wrapped in `cd $(...)`
0 commit comments