Claude Code writes a local .claude/scheduled_tasks.lock runtime lock next to the tracked .claude/settings.json. It currently shows up as untracked in git status and risks being swept into a git add -A. This adds a targeted ignore for it.

Scoped to the lock file only — .claude/settings.json stays tracked, and .claude/settings.local.json is already ignored.

🧑‍💻🤖 — posted via Claude Code

Greptile Summary

Adds .claude/scheduled_tasks.lock to .gitignore to prevent Claude Code's runtime lock file from appearing as untracked and accidentally being staged. Also fixes a missing trailing newline from the prior .claude-workspace/ entry.

• Scoped ignore targets only the lock file, leaving .claude/settings.json tracked and .claude/settings.local.json (already ignored) unaffected.
• No logic or source code changes; purely a housekeeping update to the ignore list.

Confidence Score: 5/5

Safe to merge — adds a single targeted .gitignore entry with no effect on tracked files or source code.

The change is limited to one line in .gitignore plus a comment, correctly scoped to the Claude Code runtime lock file. It also fixes a pre-existing missing newline. No source files, configs, or tracked .claude/ files are affected.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Claude Code runs] --> B[Writes .claude/scheduled_tasks.lock]
    B --> C{git status}
    C -->|Before PR| D[Lock file appears as untracked]
    C -->|After PR| E[Lock file ignored by .gitignore]
    D --> F[Risk: accidentally staged by git add -A]
    E --> G[Safe: never staged or committed]

Reviews (1): Last reviewed commit: "chore: gitignore .claude/scheduled_tasks..." | Re-trigger Greptile