yard-timekeeper: Stop YARD Timestamp Churn in Checked-In Docs
The article discusses the release of yard-timekeeper v0.1.0, a RubyGem designed to reduce unnecessary timestamp churn in YARD-generated documentation. This tool helps maintain cleaner version control by restoring files that only have timestamp changes, thus preserving meaningful documentation edits. It aims to streamline the documentation process for Ruby projects while minimizing build noise in version control systems.
- ▪Yard-timekeeper v0.1.0 is a RubyGem that addresses timestamp churn in YARD documentation.
- ▪The tool restores files with only timestamp changes, keeping real content changes intact.
- ▪It is intended to improve the review process by reducing noise in pull requests.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
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 | DEV.to (Top) |
| Canonical URL | https://dev.to/galtzo/yard-timekeeper-stop-yard-timestamp-churn-in-checked-in-docs-369o |
| Publication time | Sun, 24 May 2026 00:35:28 +0000 |
| Retrieval time | 2026-05-24T01:07:28.629Z |
| Last seen | 2026-05-24T01:07:28.629Z |
| 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 | _-nW9HNvyUoe |
| 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
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 561326) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Peter H. Boling Posted on May 24 yard-timekeeper: Stop YARD Timestamp Churn in Checked-In Docs #ruby #rubygem #yard #opensource 🕰️ I just released yard-timekeeper v0.1.0, a small RubyGem for Ruby projects that check generated YARD HTML into git. It solves a very specific kind of documentation noise: timestamp-only churn. The Problem If your project publishes generated YARD documentation from a checked-in docs/ directory, you have probably seen this: You run the docs task.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
