Two Git ignore files nobody told me about
I learned it the easy way, by watching a colleague learn it the hard way: furiously rewriting history to cover his tracks, then rotating cloud credentials in a panic.These days the untracked files are harmless. Random markdown notes and, more often than not, agent plans. They go stale fast, and I'm not convinced they're worth the effort.So why put up with a permanently dirty working tree?
- ▪I learned it the easy way, by watching a colleague learn it the hard way: furiously rewriting history to cover his tracks, then rotating cloud credentials in a panic.These days the untracked files are harmless.
- ▪Random markdown notes and, more often than not, agent plans.
- ▪They go stale fast, and I'm not convinced they're worth the effort.So why put up with a permanently dirty working tree?
Hacker News (Front Page) files mainly under programming. We currently carry 2,045 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Dinculescu |
| Canonical URL | https://mihai.dinculescu.dev/posts/two-git-ignore-files-nobody-told-me-about/ |
| Publication time | Wed, 23 Sep 2026 11:28:47 +0000 |
| Retrieval time | 2026-09-23T14:09:30.753Z |
| Last seen | 2026-09-23T14:09:30.753Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | IBFccOV5f0BW · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Two git ignore files nobody told me aboutPosted on 2026-09-23 :: 4 Min Read :: Source Code:: claude-code git One of my many bad habits is carrying untracked files around in the repositories I work on.I did learn, some time ago, that those files must never contain secrets, because sooner or later they get committed by mistake. I learned it the easy way, by watching a colleague learn it the hard way: furiously rewriting history to cover his tracks, then rotating cloud credentials in a panic.These days the untracked files are harmless. Random markdown notes and, more often than not, agent plans. I haven't started committing those yet.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Dinculescu.
Discussion
0 commentsMore from Dinculescu
