setup.sh does not generate .gitignore for new projects

[serejke]

Bug

ralph-setup (via setup.sh) does not create a .gitignore in newly created projects. This causes Ralph's runtime/service files to be tracked by git.

Expected behavior

New projects created with ralph-setup my-project should include a .gitignore that excludes Ralph's runtime files, matching the patterns already defined in create_files.sh (lines 672-720).

Current behavior

setup.sh copies PROMPT.md, fix_plan.md, AGENT.md, and generates .ralphrc, but never creates a .gitignore. As a result, files like .ralph/.call_count, .ralph/status.json, .ralph/logs/*, and other transient state files get committed to git on the first ralph run.

Root cause

create_files.sh contains a comprehensive .gitignore (lines 672-720) but it's only written into the ralph-claude-code tool repository itself. setup.sh doesn't reference or replicate it for new projects.

Suggested fix

Either:

1. Add a .gitignore template to templates/ and copy it in setup.sh (consistent with how other templates are handled), or
2. Generate it inline in setup.sh (like .ralphrc is generated)

The .gitignore should include at minimum:

.ralph/.call_count
.ralph/.last_reset
.ralph/.loop_start_sha
.ralph/.exit_signals
.ralph/.circuit_breaker_state
.ralph/.circuit_breaker_history
.ralph/.ralph_session
.ralph/.ralph_session_history
.ralph/.claude_session_id
.ralph/.response_analysis
.ralph/progress.json
.ralph/status.json
.ralph/live.log
.ralph/logs/*
!.ralph/logs/.gitkeep
.ralph/docs/generated/*
!.ralph/docs/generated/.gitkeep

Affected versions

Current main branch. Also affects ralph-enable and ralph-enable-ci (checked lib/enable_core.sh — same omission).

[coderabbitai]

🔗 Related PRs

#60 - test(setup): add 36 comprehensive tests for setup.sh [merged]
#137 - fix(setup): create .ralphrc with consistent tool permissions [merged]
#155 - fix: setup.sh and install.sh improvements [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[traycerai]

Plan

Observations

The issue is confirmed: neither setup.sh nor lib/enable_core.sh creates a .gitignore file for new or enabled projects. The comprehensive .gitignore template exists in file:create_files.sh (lines 672-721) but is only used for the ralph-claude-code repository itself. This causes Ralph's runtime files (.ralph/.call_count, .ralph/status.json, .ralph/logs/*, etc.) to be tracked by git. The codebase follows a pattern where templates are stored in templates/ directory and copied during setup, while configuration files like .ralphrc are generated inline.

Approach

The fix will follow the existing template pattern for consistency. A .gitignore template will be added to the templates/ directory, then copied during project setup and enablement. This approach is preferred over inline generation because: (1) it's consistent with how other templates (PROMPT.md, fix_plan.md, AGENT.md) are handled, (2) it makes the .gitignore easier to maintain and update, and (3) it allows users to customize the template if needed. The implementation will modify three files: create a new template, update setup.sh, and update lib/enable_core.sh.

Implementation Steps

1. Create .gitignore Template

File: file:templates/.gitignore

Create a new template file in the templates/ directory with the comprehensive .gitignore content from file:create_files.sh (lines 673-721). This template should include:

• Ralph runtime files (.ralph/.call_count, .ralph/.last_reset, .ralph/.exit_signals, etc.)
• Ralph logs and generated docs (.ralph/logs/*, .ralph/docs/generated/*)
• General logs (*.log)
• OS files (.DS_Store, Thumbs.db)
• Temporary files (*.tmp, .temp/)
• Language-specific patterns (node_modules/, __pycache__/, target/)
• IDE files (.vscode/, .idea/, *.swp)
• Ralph backup directories (.ralph_backup_*)

The template should use the exact content from lines 674-720 of file:create_files.sh (excluding the cat > .gitignore << 'EOF' wrapper).

2. Update setup.sh

File: file:setup.sh

Modify the template copying section (around lines 44-48) to include .gitignore:

Location: After line 48 where AGENT.md is copied

Add a new line to copy the .gitignore template from $TEMPLATES_DIR/.gitignore to the project root (not inside .ralph/). This should be placed before the .ralphrc generation section (line 50).

Verification: The .gitignore should be copied before the git initialization (line 96) so that the initial commit respects the ignore rules.

3. Update lib/enable_core.sh

File: file:lib/enable_core.sh

Modify the enable_ralph_in_directory() function to create .gitignore:

Location: In the file generation section (around lines 768-793), after creating .ralph/fix_plan.md (line 778) and before generating .ralphrc (line 792)

Add logic to:

1. Get the templates directory using get_templates_dir() function (already exists at line 467)
2. Read the .gitignore template content
3. Use safe_create_file() to create .gitignore in the project root (this respects the ENABLE_FORCE flag and won't overwrite existing .gitignore files unless forced)

Implementation approach:

• Check if $TEMPLATES_DIR/.gitignore exists
• If it exists, read its content and use safe_create_file ".gitignore" "$gitignore_content"
• If template doesn't exist, log a warning but don't fail (graceful degradation)

4. Update create_files.sh (Optional Cleanup)

File: file:create_files.sh

Location: Lines 672-721

Consider adding a comment indicating that this .gitignore is for the ralph-claude-code repository itself, and that the template version is maintained in templates/.gitignore. This helps prevent confusion about which file is the source of truth.

Alternatively, modify this section to copy from templates/.gitignore instead of generating inline, ensuring both locations stay in sync.

5. Verification Points

After implementation, verify:

1. New projects (ralph-setup my-project): Should have .gitignore in project root
2. Enabled projects (ralph enable): Should have .gitignore created (if not exists)
3. Forced enable (ralph enable --force): Should overwrite existing .gitignore
4. Existing .gitignore: Should be preserved when running ralph enable without --force
5. Template missing: Should handle gracefully if templates/.gitignore doesn't exist

6. Testing Scenarios

Test the following scenarios:

1. Run ralph-setup new-project and verify .gitignore exists with correct content
2. Run ralph enable in existing project without .gitignore - should create it
3. Run ralph enable in project with existing .gitignore - should skip (log "SKIP")
4. Run ralph enable --force in project with existing .gitignore - should overwrite
5. Run ralph enable-ci - should create .gitignore (uses same enable_ralph_in_directory())
6. Verify git doesn't track Ralph runtime files after first ralph run

Affected Files Summary

graph TD
    A[templates/.gitignore] -->|copied by| B[setup.sh]
    A -->|read by| C[lib/enable_core.sh]
    B -->|creates| D[New Project .gitignore]
    C -->|creates| E[Enabled Project .gitignore]
    F[ralph_enable.sh] -->|uses| C
    G[ralph_enable_ci.sh] -->|uses| C
    H[create_files.sh] -.->|reference| A

Loading

Files to modify:

• file:templates/.gitignore (create new)
• file:setup.sh (add copy command)
• file:lib/enable_core.sh (add .gitignore creation in enable_ralph_in_directory())
• file:create_files.sh (optional: add reference comment)

Files indirectly affected:

• file:ralph_enable.sh (uses enable_ralph_in_directory())
• file:ralph_enable_ci.sh (uses enable_ralph_in_directory())

Import In IDE

🤖 Prompt for AI Agents

## Observations

The issue is confirmed: neither `setup.sh` nor `lib/enable_core.sh` creates a `.gitignore` file for new or enabled projects. The comprehensive `.gitignore` template exists in `file:create_files.sh` (lines 672-721) but is only used for the ralph-claude-code repository itself. This causes Ralph's runtime files (`.ralph/.call_count`, `.ralph/status.json`, `.ralph/logs/*`, etc.) to be tracked by git. The codebase follows a pattern where templates are stored in `templates/` directory and copied during setup, while configuration files like `.ralphrc` are generated inline.

## Approach

The fix will follow the existing template pattern for consistency. A `.gitignore` template will be added to the `templates/` directory, then copied during project setup and enablement. This approach is preferred over inline generation because: (1) it's consistent with how other templates (PROMPT.md, fix_plan.md, AGENT.md) are handled, (2) it makes the .gitignore easier to maintain and update, and (3) it allows users to customize the template if needed. The implementation will modify three files: create a new template, update `setup.sh`, and update `lib/enable_core.sh`.

## Implementation Steps

### 1. Create .gitignore Template

**File:** `file:templates/.gitignore`

Create a new template file in the `templates/` directory with the comprehensive .gitignore content from `file:create_files.sh` (lines 673-721). This template should include:

- Ralph runtime files (`.ralph/.call_count`, `.ralph/.last_reset`, `.ralph/.exit_signals`, etc.)
- Ralph logs and generated docs (`.ralph/logs/*`, `.ralph/docs/generated/*`)
- General logs (`*.log`)
- OS files (`.DS_Store`, `Thumbs.db`)
- Temporary files (`*.tmp`, `.temp/`)
- Language-specific patterns (`node_modules/`, `__pycache__/`, `target/`)
- IDE files (`.vscode/`, `.idea/`, `*.swp`)
- Ralph backup directories (`.ralph_backup_*`)

The template should use the exact content from lines 674-720 of `file:create_files.sh` (excluding the `cat > .gitignore << 'EOF'` wrapper).

### 2. Update setup.sh

**File:** `file:setup.sh`

Modify the template copying section (around lines 44-48) to include `.gitignore`:

**Location:** After line 48 where `AGENT.md` is copied

Add a new line to copy the `.gitignore` template from `$TEMPLATES_DIR/.gitignore` to the project root (not inside `.ralph/`). This should be placed before the `.ralphrc` generation section (line 50).

**Verification:** The `.gitignore` should be copied before the git initialization (line 96) so that the initial commit respects the ignore rules.

### 3. Update lib/enable_core.sh

**File:** `file:lib/enable_core.sh`

Modify the `enable_ralph_in_directory()` function to create `.gitignore`:

**Location:** In the file generation section (around lines 768-793), after creating `.ralph/fix_plan.md` (line 778) and before generating `.ralphrc` (line 792)

Add logic to:
1. Get the templates directory using `get_templates_dir()` function (already exists at line 467)
2. Read the `.gitignore` template content
3. Use `safe_create_file()` to create `.gitignore` in the project root (this respects the `ENABLE_FORCE` flag and won't overwrite existing .gitignore files unless forced)

**Implementation approach:**
- Check if `$TEMPLATES_DIR/.gitignore` exists
- If it exists, read its content and use `safe_create_file ".gitignore" "$gitignore_content"`
- If template doesn't exist, log a warning but don't fail (graceful degradation)

### 4. Update create_files.sh (Optional Cleanup)

**File:** `file:create_files.sh`

**Location:** Lines 672-721

Consider adding a comment indicating that this .gitignore is for the ralph-claude-code repository itself, and that the template version is maintained in `templates/.gitignore`. This helps prevent confusion about which file is the source of truth.

Alternatively, modify this section to copy from `templates/.gitignore` instead of generating inline, ensuring both locations stay in sync.

### 5. Verification Points

After implementation, verify:

1. **New projects** (`ralph-setup my-project`): Should have `.gitignore` in project root
2. **Enabled projects** (`ralph enable`): Should have `.gitignore` created (if not exists)
3. **Forced enable** (`ralph enable --force`): Should overwrite existing `.gitignore`
4. **Existing .gitignore**: Should be preserved when running `ralph enable` without `--force`
5. **Template missing**: Should handle gracefully if `templates/.gitignore` doesn't exist

### 6. Testing Scenarios

Test the following scenarios:

1. Run `ralph-setup new-project` and verify `.gitignore` exists with correct content
2. Run `ralph enable` in existing project without `.gitignore` - should create it
3. Run `ralph enable` in project with existing `.gitignore` - should skip (log "SKIP")
4. Run `ralph enable --force` in project with existing `.gitignore` - should overwrite
5. Run `ralph enable-ci` - should create `.gitignore` (uses same `enable_ralph_in_directory()`)
6. Verify git doesn't track Ralph runtime files after first `ralph` run

## Affected Files Summary

```mermaid
graph TD
    A[templates/.gitignore] -->|copied by| B[setup.sh]
    A -->|read by| C[lib/enable_core.sh]
    B -->|creates| D[New Project .gitignore]
    C -->|creates| E[Enabled Project .gitignore]
    F[ralph_enable.sh] -->|uses| C
    G[ralph_enable_ci.sh] -->|uses| C
    H[create_files.sh] -.->|reference| A
```

**Files to modify:**
- `file:templates/.gitignore` (create new)
- `file:setup.sh` (add copy command)
- `file:lib/enable_core.sh` (add .gitignore creation in `enable_ralph_in_directory()`)
- `file:create_files.sh` (optional: add reference comment)

**Files indirectly affected:**
- `file:ralph_enable.sh` (uses `enable_ralph_in_directory()`)
- `file:ralph_enable_ci.sh` (uses `enable_ralph_in_directory()`)

---

Execution Information

Branch: main
Commit: b77cc99

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.