Git Can Track a File and Ignore It Simultaneously — Here's Why That Happens

·1 views

A developer discovered that CLAUDE.md, a rules file for Claude Code sessions, has been simultaneously tracked by git and listed in the repository's .gitignore since the very first commit that created both. This contradiction exists because git's ignore rules only apply to untracked files — once a file is added to the index, .gitignore no longer governs it. Both the file and the ignore rule were introduced in the same commit, meaning the file was explicitly staged before the ignore rule could take effect. The standard diagnostic command, git check-ignore, returns no output for such files by default, misleading developers into thinking the ignore rule is invalid, when the correct flag --no-index is needed to verify the pattern match. If the file were ever accidentally untracked and removed, git would refuse to re-add it, making the silent conflict a latent operational risk.

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)

How one developer made AI-generated code safe to merge without manual review

A developer running multiple AI coding agents in parallel found the daily volume of code changes exceeded what any human could feasibly review in a working day. Rather than reducing output, he restructured his workflow so that potential issues are caught automatically before code reaches the review stage. He achieved this by enforcing strict linting rules — including complexity limits and TypeScript strict presets — as hard errors that AI agents, unlike human engineers, never push back against. Exceptions to these rules are tracked in a visible config file with written justifications, making rule erosion easy to spot. Critical logic is also extracted into pure, tested functions so that decisions made by automated tools remain verifiable and auditable.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds CSS-Only Salvadoran Pupusa Scene With Day-Night Light Switch

A developer from El Salvador has created a fully CSS-rendered illustration of a traditional pupusa table as a submission to the Frontend Challenge Comfort Food Edition. The artwork depicts pupusas — El Salvador's national dish of stuffed corn tortillas — served with curtido and tomato salsa, evoking the atmosphere of a nighttime street food stall. Built using only CSS gradients, blend modes, and border-radius with just 15 lines of JavaScript for class toggles, the piece features no images, SVG, or external libraries. Interactive buttons let users pour salsa over the pupusas or switch the scene to a candlelit night mode using a single overlay div with mix-blend-mode. The project also incorporates accessibility features including ARIA roles, labeled buttons, and a prefers-reduced-motion setting that freezes animations rather than removing them entirely.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

React Hooks Explained: useState, useEffect, useContext, and useRef

React Hooks transformed modern React development by enabling state and side effect management directly inside functional components, eliminating the need for class components. Before Hooks, developers faced challenges such as complex lifecycle methods, confusing 'this' bindings, and deeply nested component structures from Higher-Order Components. Core Hooks include useState for local state, useEffect for side effects like API calls and subscriptions, and useContext for accessing shared values across a component tree without prop-drilling. The useRef Hook allows developers to persist mutable values across renders and interact directly with DOM elements without triggering re-renders. Together, these Hooks make React code cleaner, easier to test, and simpler to maintain.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Tutorial Claims 20% Latency Cut Using Node.js Multi-Agent Workflow with qm Library

A developer published a tutorial on DEV Community detailing how to reduce AI agent task completion times by 20% using a Node.js workflow built on qm, a lightweight agent orchestration library. The author drew on experience building multi-agent systems, including a gold trading platform and a YouTube automation pipeline, to illustrate common coordination challenges such as deadlocks and high latency. The tutorial centers on a parallel delegation pattern where a primary ResearchAgent breaks a broad request into sub-tasks and distributes them concurrently to specialized SentimentAgents. The author argues that standard qm examples assume linear flows and that explicit concurrency management is needed for real-world, dynamic task splitting. Code snippets using Node.js and the OpenAI API are provided to demonstrate the orchestration setup.

0 comments Read more at DEV Community