[Feature] 默认忽略 .lithe/.gitignore 自身，避免进入 Git 待提交列表
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- git
- Domain
- tooling
Research direction
The change concerns the .lithe/.gitignore file that Lithe generates, which must also ignore itself. Start by finding the code that writes this default ignore file, since the payload does not name it. Done means new projects get a .gitignore line, existing files gain that line while keeping user rules, and .lithe/.gitignore no longer shows as untracked in JetBrains.
Written by the indexing model from the issue text.
Description
Problem to solve / 要解决的问题
Lithe 生成的 .lithe/.gitignore 未忽略自身，使用 JetBrains 打开同一项目时，会出现在 Git 未跟踪文件列表中，需要手动处理。
Proposed solution / 建议方案
在自动生成的 .lithe/.gitignore 中加入 .gitignore，保留现有规则：
.gitignore
/run/local.json
/run/classes/
**/*.tmp
已有文件在维护忽略规则时补齐这一项，保留用户原有内容。团队共享配置仍可按需提交。
Target platform / 目标平台
Cross-platform / 跨平台
Area / 模块
Project and workspace / 项目与工作区
Priority / 优先级
P2 / 后续考虑：目前不着急，可安排到后续版本
Alternatives considered / 已考虑的替代方案
只写 * 会同时忽略团队共享配置，因此建议仅补充忽略 .gitignore 自身。
Additional context / 补充信息
用户已提供截图，显示 .lithe/.gitignore 出现在 JetBrains 的未跟踪文件列表中；现有规则为 /run/local.json、/run/classes/、**/*.tmp。
截图依次为：.lithe 目录结构、JetBrains 未跟踪文件提示、建议增加的忽略规则。
Checklist / 提交前检查
- I searched existing issues for duplicates. / 我已搜索现有 Issue，确认没有重复建议。
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 151
- Avg merge
- 11h 26m
- Merged PRs (30d)
- 429
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from 1lck/Lithe-IDEA
-
area:editor bug P0 platform:macos review: low
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
1lck/Lithe-IDEA#1118 · 2 comments ·
Maintainers usually reply within 1 day
-
bug issue-form:bug review: low
Difficulty 4/5 3-5 days Newbie friendliness 48/100
1lck/Lithe-IDEA#1761 ·
Maintainers usually reply within 1 day
-
[Bug] 一直报错Indexing policy changedPossibly taken A pull request linked to this issue is open or already merged. Openbug issue-form:bug review: low
Difficulty 4/5 3-5 days Newbie friendliness 48/100
1lck/Lithe-IDEA#1749 ·
Maintainers usually reply within 1 day
-
area:logging enhancement P2 platform:macos review: high
Difficulty 5/5 Over a week Newbie friendliness 25/100
1lck/Lithe-IDEA#1721 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug]终端窗口放在右侧时，调整大小超过屏幕一半时点一下或者再次调整大小会直接跳到初始大小，往小调整正常Possibly taken @arkleselect claimed this 1 day ago. Openreview: low
Difficulty 3/5 1-2 days Newbie friendliness 35/100
1lck/Lithe-IDEA#1703 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
S: triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
iot client
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Open-Locker/Open-Locker#365 ·
Maintainers usually reply within 1 day
-
bug enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
inmanta/web-console#7787 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
shoelace-style/webawesome#2979 ·
Maintainers usually reply within 1 day