RepoGhost Uses Git History and Semantic Search to Recover Forgotten Design Decisions

·8 views

A developer built RepoGhost, a local tool that helps programmers investigate why past design choices were made in their Git repositories. It searches real commit messages, changed file paths, and diff excerpts, returning verifiable evidence such as commit hashes, dates, and patches. The tool also includes a Lost Files area for read-only previews of deleted text files without modifying the repository. It uses the open-weight sentence-transformers/all-MiniLM-L6-v2 model for semantic matching, which is compared against a simple keyword baseline. The project was submitted to the Hacktoberfest Open-Source AI Challenge and includes automated tests and CI.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Free Companies House data lets users find newly registered UK companies by town

A guide explains how to use Companies House's free monthly snapshot of live UK company data to identify recently incorporated firms in a given town, requiring no API key or signup. The dataset is a large CSV with one row per company, including name, number, registered postcode and town, status, incorporation date and SIC industry code. The author shares a short Python script that filters by town and recent incorporation date, reporting that it ran in about 30 seconds on a small VPS and returned 146 active Leicester companies over a 40-day window. The article notes limitations: the data reflects registered-office addresses, which may belong to accountants, contains no contact details, and is only updated monthly, with a real-time option requiring a free API key. It also advises checking the Companies House licence and UK marketing rules before commercial use.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Supabase to require explicit GRANTs on new public tables from 30 October 2026

From 30 October 2026, Supabase will stop automatically granting table access to the anon, authenticated and service_role roles on new tables in the public schema. Existing tables will keep their current permissions, but any new table exposed through the Data API will need an explicit Postgres GRANT before apps can reach it. Supabase says the change addresses AI agents and tools creating tables without human review, which previously made it easy to expose data before securing it. Developers whose AI-built apps call public tables through the Data API may see new features fail with 401 or 403 errors, which the Supabase docs describe as a missing grant. The change is enforced on all existing projects on that date, according to Supabase's changelog.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AQEMU 1.6.0 Compared With Hyper-V, VirtualBox, VMware and Plain QEMU on Windows

A developer has published a side-by-side comparison of AQEMU 1.6.0, a graphical front end for QEMU, against Hyper-V, VirtualBox 7.2, VMware Workstation Pro and plain QEMU on Windows. The table covers Windows on ARM64 support, hardware acceleration, retro guest operating systems, non-x86 guest architectures, graphical configuration, file transfer, licensing and pricing. The author notes that the other tools' information comes from their official documentation, and marks unverified items as not documented. The author argues that mainstream hypervisors remain the better choice for fast x64 Windows or Linux virtual machines. AQEMU is positioned for scenarios those tools do not cover, such as DOS, Windows 9x, and non-x86 architectures.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developers Are Freed to Use Any Language, and Old Projects Can Be Revived

The author argues that developers can now move beyond familiar languages, since recent AI-driven tools make unfamiliar technologies like Rust, C, or Go accessible. Long-term care and craftsmanship, rather than simply building and abandoning projects, are presented as what makes software genuinely valuable. Revisiting an old project by switching its technology stack can revive it, and the author shares a personal example involving a TODO list app. The discussion in the comments extends this into a broader reflection on how measuring every hour by productivity and money has made purely enjoyable coding harder to justify.

0 comments Read more at DEV Community