Best of Git — October 2025

  1. 1
    Article
    Avatar of devtoDEV·28w

    Why Do You Push Code During Work Hours?" - How an Interview Question Led Me to Build a Delayed Commit Feature

    A developer built a delayed commit feature for GoCommit after an interviewer questioned their GitHub commit timestamps during work hours. The tool allows developers to schedule commits outside restricted hours, addressing privacy concerns and work-life boundaries. It intercepts commits during configured work hours, presents alternative timestamps, and uses Git's native date flags to set both author and committer dates. The feature integrates with GoCommit's AI-powered commit message generator and raises questions about whether coding schedules should be public information.

  2. 2
    Video
    Avatar of bigboxswebigboxSWE·29w

    Extremely Underrated Programming Skills

    Shell proficiency, Git workflows, and build systems are foundational skills that significantly improve developer productivity. Mastering shell commands beyond basic navigation, understanding Git operations like rebase, stash, and reflog, and comprehending build systems can save hours of development time. These tools provide speed, control, and reliability in daily development work, making them more valuable than chasing trendy technologies.

  3. 3
    Article
    Avatar of uiwf7xowejrt4dhwsv7xiPaul Vasile·31w

    If You Say “Never Do X” in Programming, I Assume You Don’t Know What You’re Talking About

    A critique of absolute programming advice that uses blanket "never do X" statements. The author argues that most programming practices labeled as forbidden actually have legitimate use cases and context matters more than rigid rules. Examples include git force push, committing to main branches, and password management strategies. The piece advocates for understanding the purpose and appropriate context of tools rather than following dogmatic prohibitions.

  4. 4
    Video
    Avatar of primeagenThePrimeTime·28w

    banned from github

    A developer reflects on the risks of platform dependency after witnessing a GitHub account suspension. The incident highlights how relying on centralized services like GitHub for code hosting, authentication, and SSO creates single points of failure that could lock users out of their work and connected services. While self-hosting offers independence, the practical challenges and network effects of platforms like GitHub make migration difficult, leaving developers in a convenience-versus-control dilemma with no clear solution.

  5. 5
    Article
    Avatar of phoronixPhoronix·30w

    Git Developers Talk About Potentially Releasing Git 3.0 By The End Of Next Year

    Git developers are discussing plans to potentially release Git 3.0 by the end of next year. Recent conversations among the development team have centered around the timeline and scope for this major version release of the widely-used version control system.

  6. 6
    Article
    Avatar of phProduct Hunt·28w

    Twigg: Git for LLMs - a Context Management Tool

    Twigg is a context management tool that provides an improved interface for working with large language models on long-term projects. It features an interactive tree diagram to visualize entire LLM conversations and offers granular control over the context sent to language models, functioning similarly to how Git manages code versions.

  7. 7
    Article
    Avatar of github_updatesGitHub Changelog·31w

    One-click merge conflict resolution now in the web interface

    GitHub now allows developers to resolve merge conflicts directly in the web interface with one-click buttons. When a pull request has conflicts, users can choose to accept incoming changes, current changes, or both without leaving their browser. This feature brings the convenience of code editor merge tools like those in Visual Studio Code to the GitHub web workflow, eliminating the need to switch contexts or use local development environments.

  8. 8
    Article
    Avatar of hnHacker News·31w

    Who needs git when you have 1M context windows?

    A developer accidentally lost code that improved their machine learning model by 5% after refactoring without committing changes. Unable to reproduce the results, they discovered that Gemini 2.5 Pro's 1M token context window had retained the original code from their development session, allowing them to recover the lost improvements through a simple prompt.

  9. 9
    Article
    Avatar of khokbmumuz4w1vbvtnmldClaudette·31w

    Be Very Afraid

  10. 10
    Article
    Avatar of steveklabnikSteve Klabnik·29w

    I see a future in jj

    Steve Klabnik shares his decision to join ERSC, a new company building a developer collaboration platform on top of jj, a modern version control system. Drawing parallels to his early involvement with Rust, he explains why jj has strong potential: it offers incremental adoption over Git, has backing from Google with significant internal usage, features a dedicated team with deep source control expertise, and is building a passionate community. The post details his framework for evaluating promising technology projects through market fit, team strength, and user base potential.

  11. 11
    Article
    Avatar of lobstersLobsters·31w

    Conventional Commits considered harmful

    A critical examination of Conventional Commits arguing that enforcing structured commit message formats creates unnecessary barriers for contributors. The author shares a personal experience with Doom Emacs where commit linters blocked valid contributions, highlighting how the convention adds mental overhead without providing meaningful benefits for most projects. The piece contends that information captured in conventional commits is redundant with PR descriptions, and suggests alternative approaches like file-based CI/CD triggers or PR comments are more practical and less restrictive for open source collaboration.

  12. 12
    Article
    Avatar of nickjanetakisNick Janetakis·30w

    Build Docker Images in a Git Repo but Only Committed Changes — Nick Janetakis

    Learn how to build Docker images from only committed code in a Git repository using Git worktrees instead of stashing. The technique creates a temporary worktree directory containing the committed code, builds the Docker image from that location, and then cleans up the worktree. This approach avoids the risks of accidentally overwriting stashed changes while ensuring deployments only include committed code.

  13. 13
    Article
    Avatar of itsfossIt's Foss·31w

    How I am Using Git and Obsidian for Note Version Management

    A step-by-step guide to integrating Git version control with Obsidian note-taking app on Linux. Covers creating a private GitHub repository, installing Git and GitHub CLI, authenticating credentials, cloning the repo, configuring .gitignore for Obsidian files, and using the Obsidian Git plugin to stage, commit, push, and pull changes. Provides a free cloud sync solution for markdown notes with full version history.

  14. 14
    Article
    Avatar of everythingastroEverything Astro·28w

    Turn your static site visually editable for non-technical clients & teammates

    Sitepins is a visual CMS that connects to Git repositories, enabling non-technical users to edit static site content without code. It supports popular static site generators like Astro, Next.js, and Hugo, offers a WYSIWYG editor with Markdown support, maintains Git version control, includes media management, and features AI-powered content generation. The tool allows developers to maintain their workflow while giving clients and teammates direct content editing capabilities.

  15. 15
    Article
    Avatar of lobstersLobsters·29w

    Forgejo v13.0 is available

    Forgejo v13.0 introduces content moderation tools allowing users and admins to report abusive content, enhanced security with improved 2FA enforcement and Actions secrets encryption, and better Actions usability with access to previous run attempts and static workflow validation. Additional features include Pagure repository migration, EXIF data removal from avatars, CI status display on force pushes, and improved markdown editor shortcuts. The release follows a three-month cycle with v11.0 receiving long-term support until July 2026.

  16. 16
    Article
    Avatar of devtoDEV·30w

    I Built Git from Scratch to Finally Understand What I've Been Using for Years

    A developer built Veridian, a simplified version control system in Rust, to understand Git's internals. Git is fundamentally a content-addressable storage system using three object types: blobs (file contents), trees (directory listings), and commits (snapshots with metadata). All objects are stored as SHA-1 hashed, zlib-compressed files in .git/objects. Branches are just text files containing commit hashes. The project revealed that Git's complexity comes from how it's taught, not its underlying architecture. Building a basic version control system with init, hash-object, write-tree, and commit-tree commands provides deeper understanding than reading documentation.

See all Git archives