-
Notifications
You must be signed in to change notification settings - Fork 745
Expand file tree
/
Copy path.gitignore
More file actions
192 lines (163 loc) · 6.06 KB
/
Copy path.gitignore
File metadata and controls
192 lines (163 loc) · 6.06 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
*~
*#
*.swp
*.log
*.DS_Store
__pycache__/
*.py[cod]
*$py.class
*.egg-info/
/.coverage
/.coverage.*
/.cache
/.pytest_cache
/.mypy_cache
/.hypothesis
/.testmondata*
/doc/_apidoc/
/build
# Python build artifacts (wheels / sdists from `python -m build` / `make wheel`)
/dist/
# Generated agent config — contains machine-specific absolute paths
.kiro/agents/kirocrew.json
# Generated per-machine by install_cc_agent_config()
.mcp.json
# No trailing slash: a slash matches a DIRECTORY only, and a venv is commonly a
# SYMLINK in a git worktree (one interpreter shared by several checkouts). With the
# slash, `git add -A` in a worktree stages that symlink -- and the brand gate is
# what catches it, reporting `.venv` as a changed file it cannot decode as UTF-8.
/venv
/.venv
/.venv-x86
/.venv311
# Editor / IDE
.vscode/
.idea/
pyrightconfig.json
*.sublime-*
# Environment (machine-specific paths)
.env
.env.local
.install-method
# Frontend
# No trailing slash, for the same reason as the venv entries above: in a git
# worktree node_modules is often a SYMLINK to a sibling checkout's, and a slash
# matches a directory only.
node_modules
frontend/package-lock.json
frontend/dist/
tui/dist/
frontend/tsconfig.app.tsbuildinfo
frontend/tsconfig.node.tsbuildinfo
src/kiro_crew/static/dist/
src/kiro_crew/static/dist
# Staged copies static/dist links to, the link being swapped in, and the
# staging lock (src/kiro_crew/frontend.py). An untracked leftover here makes
# the checkout read as dirty, which fail-closes Dev Fleet's "Prune merged".
src/kiro_crew/static/.dist.*
# Disposable scratch for Dev Fleet's Pull+Build installability probe
# (npm_preflight). It lives in the checkout rather than TMPDIR so the rehearsal
# runs on the filesystem the real `npm ci` writes to; probe() removes it in a
# `finally`, and this rule covers the one a killed process leaves. Same
# consequence as the staging entries above: an untracked leftover makes the
# checkout read as dirty and fail-closes "Prune merged".
/.kirocrew-npm-preflight-*
# Build-time provenance stamp (scripts/stamp-distribution.sh). Generated per
# packaging path; a committed copy would mislabel every other build's beacon.
src/kiro_crew/_build_info.py
# JVM crash logs
hs_err_pid*.log
# OS
Thumbs.db
.git.old
# Dev mode data directory
.kirocrew-dev/
.kirocrew-dev2/
# Potential task progress files
*.TASK_PROGRESS.md
docs/TASK_PLAN_MODE.md
frontend/src/.backup_pre_mdpanel/
kirocrew-data.tar.gz
.kiro/hooks/track-with-agent.kiro.hook
# Agent-workflow scratch — files agents sometimes write into a worktree and
# forget to remove: a PR body fed to `gh pr create --body-file`, and review-round
# build/test log dirs (e.g. .r29-logs/). Ignoring them keeps `git status` clean so
# Dev Fleet "Prune merged" can reap merged worktrees (a dirty tree fail-closes the
# prune as merged_dirty). Prefer writing scratch under `mktemp -d`.
# (`*.log` is already ignored above.)
.pr-body.md
.r*-logs/
# PR review evidence (screenshots, GIFs, recordings) is uploaded as a GitHub
# attachment with `gh pr create|edit --attach`, never committed; non-media
# evidence goes in a PR comment -- text (JSON provenance, perf baselines) as a
# fenced block, a document (PDF, docx, zip) dragged in via the web UI. The
# capture scripts under website/scripts/ and website/capture/ still write here
# locally.
# ONE exception, for contributors WITHOUT write access on this repository:
# GitHub's attachment-upload endpoint answers READ permission with a 404
# (cli/cli#14302), so `--attach` is not available to them at all. They commit
# the media here instead -- `git add -f temp-screenshots/<dir>/shot.png`, since
# this rule ignores it by default -- and reference the repository-relative path
# from the PR body. Both UX and design review lanes read those files. The
# ignore rule stays so that nobody else's capture run dirties `git status`.
temp-screenshots/
.github/screenshots/
# Staged blind-review artifacts (kirocrew-prepare-pr review lanes point subagents at
# .review-<n>.diff files) and the autofix work-dir heartbeat — scratch, never
# a deliverable, and a `git add -A` would otherwise sweep them into the PR.
.review-*.diff
.heartbeat
# AI attribution tracking data
.attribution/
# Playwright test artifacts
frontend/test-results/
frontend/playwright-report/
frontend/.rtx.toml
# OpenClaw source checkout
openclaw-main/
TASK_PROGRESS.md
*.iml
reviews/
test_plan_atomic_writes_subagent_progress.md
# Top-level legacy electron build dir (the tracked desktop source lives in
# website/electron/). Only ignore build OUTPUTS there, not the source.
/electron/
website/electron/backend-dist/
website/electron/dist/
website/electron/node_modules
# Placed by packaging/build-desktop.sh from KIROCREW_MANAGED_INSTALL_MARKER so
# electron-builder packs it into app.asar; a per-edition build input, not source.
website/electron/EXTERNALLY-MANAGED
# Generated launcher icon (created from icon.png when making the desktop shortcut)
website/electron/KiroCrew.ico
tui/
mise.toml
# Git worktrees
.worktrees/
.attach_pid*
python3.10
FILE_SPLIT_PLAN.md
# Eval harness output
eval_results/
build-log-trimmed_*.txt
docs/APP_DEVELOPER_GUIDE.md
.claude/scheduled_tasks.lock
runs.json
.review/
# Local session summary (working notes, not part of the PR)
SESSION_SUMMARY.md
# Internal migration worklog — deliberately untracked (contains pre-scrub notes)
MOCHI_MIGRATION.md
website/.vitest-reports/
# Skill eval A/B outputs (regenerated per run; not review artifacts)
evals/*/iteration-*/
# A distribution stamps its build number here at packaging time (see
# kiro_crew/__init__.py); never committed -- a dev checkout runs the bare core.
src/kiro_crew/BUILD_VERSION
# The crew image's wheel, staged by scripts/build_crew_base_image.sh for the
# context bind mount. `vendor/` is a TRACKED directory (its .gitkeep ships in the
# sdist so the image can be built from an installed copy), so without this rule a
# ~27MB build artifact sits in a tracked path waiting for a `git add -A`.
src/kiro_crew/apps/builtins/aws_control/crew/runtime/vendor/*.whl
# Cross-process lock for workspace Kiro CLI overlay writers.
/.kiro/settings/.kirocrew-cli-settings.lock