Show HN: Gitcredits – movie-style end credits for any Git repo in your terminal

Hacker News · Feb 28, 2026 · Collected from RSS

Summary

Article URL: https://github.com/Higangssh/gitcredits Comments URL: https://news.ycombinator.com/item?id=47194679 Points: 11 # Comments: 0

Full Article

Skip to content Navigation Menu AI CODE CREATIONGitHub CopilotWrite better code with AIGitHub SparkBuild and deploy intelligent appsGitHub ModelsManage and compare promptsMCP RegistryNewIntegrate external toolsView all featuresPricing Provide feedback Saved searches Use saved searches to filter your results more quickly Sign up Appearance settings Notifications You must be signed in to change notification settings Fork 0 Star 23 Folders and filesNameNameLast commit messageLast commit dateLatest commitHistory1 Commitassetsassets.gitignore.gitignoreREADME.mdREADME.mdgo.modgo.modgo.sumgo.summain.gomain.goREADMEgitcredits Roll movie-style credits for your git repo — right in the terminal. Install Go go install github.com/Higangssh/gitcredits@latest From source git clone https://github.com/Higangssh/gitcredits.git cd gitcredits go build -o gitcredits . Usage cd your-repo gitcredits That's it. Navigate into any git repository and run gitcredits. Controls Key Action ↑ / ↓ Manual scroll q / Esc Quit What it shows ASCII art title from your repo name Project lead — top contributor by commits Contributors — everyone who committed Notable scenes — recent feat: and fix: commits Stats — total commits, contributors, GitHub stars, language, license GitHub metadata (stars, description, license) requires gh CLI to be installed and authenticated. Works without it — you'll just get git-only data. Requirements Git Go 1.21+ gh CLI (optional, for GitHub metadata) License MIT

Share this story

Read Original at Hacker News

Hacker Newsabout 2 hours ago

Verified Spec-Driven Development (VSDD)

Article URL: https://gist.github.com/dollspace-gay/d8d3bc3ecf4188df049d7a4726bb2a00 Comments URL: https://news.ycombinator.com/item?id=47197595 Points: 19 # Comments: 6

Hacker Newsabout 2 hours ago

The whole thing was a scam

Article URL: https://garymarcus.substack.com/p/the-whole-thing-was-scam Comments URL: https://news.ycombinator.com/item?id=47197505 Points: 33 # Comments: 2

Hacker Newsabout 3 hours ago

Obsidian Sync now has a headless client

Article URL: https://help.obsidian.md/sync/headless Comments URL: https://news.ycombinator.com/item?id=47197267 Points: 94 # Comments: 32

Hacker Newsabout 3 hours ago

Show HN: SQLite for Rivet Actors – one database per agent, tenant, or document

Hey HN! We posted Rivet Actors here previously [1] as an open-source alternative to Cloudflare Durable Objects. Today we've released SQLite storage for actors (Apache 2.0). Every actor gets its own SQLite database. This means you can have millions of independent databases: one for each agent, tenant, user, or document. Useful for: - AI agents: per-agent DB for message history, state, embeddings - Multi-tenant SaaS: real per-tenant isolation, no RLS hacks - Collaborative documents: each document gets its own database with built-in multiplayer - Per-user databases: isolated, scales horizontally, runs at the edge The idea of splitting data per entity isn't new: Cassandra and DynamoDB use partition keys to scale horizontally, but you're stuck with rigid schemas ("single-table design" [3]), limited queries, and painful migrations. SQLite per entity gives you the same scalability without those tradeoffs [2]. How this compares: - Cloudflare Durable Objects & Agents: most similar to Rivet Actors with colocated SQLite and compute, but closed-source and vendor-locked - Turso Cloud: Great platform, but closed-source + diff use case. Clients query over the network, so reads are slow or stale. Rivet's single-writer actor model keeps reads local and fresh. - D1, Turso (the DB), Litestream, rqlite, LiteFS: great tools for running a single SQLite database with replication. Rivet is for running lots of isolated databases. Under the hood, SQLite runs in-process with each actor. A custom VFS persists writes to HA storage (FoundationDB or Postgres). Rivet Actors also provide realtime (WebSockets), React integration (useActor), horizontal scalability, and actors that sleep when idle. GitHub: https://github.com/rivet-dev/rivet Docs: https://www.rivet.dev/docs/actors/sqlite/ [1] https://news.ycombinator.com/item?id=42472519 [2] https://rivet.dev/blog/2025-02-16-sqlite-on-the-server-is-mi... [3] https://www.alexdebrie.com/posts/dynamodb-single-table/ Comments URL: https://news.ycombinator.

Hacker Newsabout 3 hours ago

Cognitive Debt: When Velocity Exceeds Comprehension

Article URL: https://www.rockoder.com/beyondthecode/cognitive-debt-when-velocity-exceeds-comprehension/ Comments URL: https://news.ycombinator.com/item?id=47196582 Points: 197 # Comments: 79

Hacker Newsabout 4 hours ago

Show HN: Rust-powered document chunker for RAG – 40x faster, O(1) memory

I built a document chunking library for RAG pipelines with a Rust core and Python bindings. The problem: LangChain's chunker is pure Python and becomes a bottleneck at scale — slow and memory-hungry on large document sets. What Krira Chunker does differently: - Rust-native processing — 40x faster than LangChain's implementation - O(1) space complexity — memory stays flat regardless of document size - Drop-in Python API — works with any existing RAG pipeline - Production-ready — 17 versions shipped, 315+ installs pip install krira-augment Would love brutal feedback from anyone building RAG systems — what chunking problems are you running into that this doesn't solve yet? Comments URL: https://news.ycombinator.com/item?id=47196069 Points: 4 # Comments: 0

Show HN: Gitcredits – movie-style end credits for any Git repo in your terminal

Full Article

Related Articles

Verified Spec-Driven Development (VSDD)

The whole thing was a scam

Obsidian Sync now has a headless client

Show HN: SQLite for Rivet Actors – one database per agent, tenant, or document

Cognitive Debt: When Velocity Exceeds Comprehension

Show HN: Rust-powered document chunker for RAG – 40x faster, O(1) memory

Show HN: Gitcredits – movie-style end credits for any Git repo in your terminal

Full Article

Related Articles

Verified Spec-Driven Development (VSDD)

The whole thing was a scam

Obsidian Sync now has a headless client

Show HN: SQLite for Rivet Actors – one database per agent, tenant, or document

Cognitive Debt: When Velocity Exceeds Comprehension

Show HN: Rust-powered document chunker for RAG – 40x faster, O(1) memory

Related Articles

Hacker Newsabout 2 hours ago
Verified Spec-Driven Development (VSDD)
Article URL: https://gist.github.com/dollspace-gay/d8d3bc3ecf4188df049d7a4726bb2a00 Comments URL: https://news.ycombinator.com/item?id=47197595 Points: 19 # Comments: 6

Hacker Newsabout 2 hours ago
The whole thing was a scam
Article URL: https://garymarcus.substack.com/p/the-whole-thing-was-scam Comments URL: https://news.ycombinator.com/item?id=47197505 Points: 33 # Comments: 2

Hacker Newsabout 3 hours ago
Obsidian Sync now has a headless client
Article URL: https://help.obsidian.md/sync/headless Comments URL: https://news.ycombinator.com/item?id=47197267 Points: 94 # Comments: 32
Article URL: https://help.obsidian.md/sync/headless Comments URL: https://news.ycombinator.com/item?id=47197267 Points: 94 # Comments: 32

Hacker Newsabout 3 hours ago
Show HN: SQLite for Rivet Actors – one database per agent, tenant, or document
Hey HN! We posted Rivet Actors here previously [1] as an open-source alternative to Cloudflare Durable Objects. Today we've released SQLite storage for actors (Apache 2.0). Every actor gets its own SQLite database. This means you can have millions of independent databases: one for each agent, tenant, user, or document. Useful for: - AI agents: per-agent DB for message history, state, embeddings - Multi-tenant SaaS: real per-tenant isolation, no RLS hacks - Collaborative documents: each document gets its own database with built-in multiplayer - Per-user databases: isolated, scales horizontally, runs at the edge The idea of splitting data per entity isn't new: Cassandra and DynamoDB use partition keys to scale horizontally, but you're stuck with rigid schemas ("single-table design" [3]), limited queries, and painful migrations. SQLite per entity gives you the same scalability without those tradeoffs [2]. How this compares: - Cloudflare Durable Objects & Agents: most similar to Rivet Actors with colocated SQLite and compute, but closed-source and vendor-locked - Turso Cloud: Great platform, but closed-source + diff use case. Clients query over the network, so reads are slow or stale. Rivet's single-writer actor model keeps reads local and fresh. - D1, Turso (the DB), Litestream, rqlite, LiteFS: great tools for running a single SQLite database with replication. Rivet is for running lots of isolated databases. Under the hood, SQLite runs in-process with each actor. A custom VFS persists writes to HA storage (FoundationDB or Postgres). Rivet Actors also provide realtime (WebSockets), React integration (useActor), horizontal scalability, and actors that sleep when idle. GitHub: https://github.com/rivet-dev/rivet Docs: https://www.rivet.dev/docs/actors/sqlite/ [1] https://news.ycombinator.com/item?id=42472519 [2] https://rivet.dev/blog/2025-02-16-sqlite-on-the-server-is-mi... [3] https://www.alexdebrie.com/posts/dynamodb-single-table/ Comments URL: https://news.ycombinator.

Hacker Newsabout 3 hours ago
Cognitive Debt: When Velocity Exceeds Comprehension
Article URL: https://www.rockoder.com/beyondthecode/cognitive-debt-when-velocity-exceeds-comprehension/ Comments URL: https://news.ycombinator.com/item?id=47196582 Points: 197 # Comments: 79

Hacker Newsabout 4 hours ago
Show HN: Rust-powered document chunker for RAG – 40x faster, O(1) memory
I built a document chunking library for RAG pipelines with a Rust core and Python bindings. The problem: LangChain's chunker is pure Python and becomes a bottleneck at scale — slow and memory-hungry on large document sets. What Krira Chunker does differently: - Rust-native processing — 40x faster than LangChain's implementation - O(1) space complexity — memory stays flat regardless of document size - Drop-in Python API — works with any existing RAG pipeline - Production-ready — 17 versions shipped, 315+ installs pip install krira-augment Would love brutal feedback from anyone building RAG systems — what chunking problems are you running into that this doesn't solve yet? Comments URL: https://news.ycombinator.com/item?id=47196069 Points: 4 # Comments: 0