---
title: "Discussion on \"Stop committing .env files, node_modules and it.only: check your staged changes before you press Commit\" | Hashnode"
description: "Discussion on \"Stop committing .env files, node_modules and it.only: check your staged changes before you press Commit\". Most \"oops\" commits are a .env file, a huge dump, node_modules or a leftover it.only, not hard bugs. Why hooks and .gitignore miss them, how to clean up, and a free VS Code extension that checks the git index live."
url: "https://hashnode.com/posts/commitsieve-stop-committing-env-files-vscode/6abb308314f7da592909936d"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Stop committing .env files, node\_modules and it.only: check your staged changes before you press Commit](https://jaytank.hashnode.dev/commitsieve-stop-committing-env-files-vscode?utm_source=hashnode&utm_medium=feed)

Most "oops" commits are a .env file, a huge dump, node\_modules or a leftover it.only, not hard bugs. Why hooks and .gitignore miss them, how to clean up, and a free VS Code extension that checks the git index live.

Sep 29 · 10 min read · jaytank.hashnode.dev  
Read the article

-   [#git](https://hashnode.com/tag/git)
-   [#vscode-extensions](https://hashnode.com/tag/vscode-extensions)
-   [#security](https://hashnode.com/tag/security)
-   [#devops](https://hashnode.com/tag/devops)
-   [#developer-tools](https://hashnode.com/tag/developer-tools)

## Written by

[JAY TANK](https://hashnode.com/@jaytank)

@jaytank

  
[View profile](https://hashnode.com/@jaytank)

Engineering insights on building and scaling modern software.

Cloud & Platform Engineer focused on building systems that scale and endure. I explore how infrastructure, automation, and engineering practices come together to support modern software teams.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.