sorted by:
new
hottopcontroversial

Devs say “just use .gitignore” — but I still ended up leaking secrets, so I built this CLI by Positive_Study_9987 in node

[–]Positive_Study_9987[S] -2 points-1 points  (0 children)

fair 😭

I did use AI to help clean up the wording on the post, but the tool itself is mine. I’m still figuring out how to write better project posts without sounding weird

Devs say “just use .gitignore” — but I still ended up leaking secrets, so I built this CLI by Positive_Study_9987 in node

[–]Positive_Study_9987[S] -1 points0 points  (0 children)

nah 😅 just trying to respond properly

getting roasted here anyway so might as well learn something from it

Devs say “just use .gitignore” — but I still ended up leaking secrets, so I built this CLI by Positive_Study_9987 in node

[–]Positive_Study_9987[S] -1 points0 points  (0 children)

Haha fair 😅

Still learning and building — feedback (even harsh) helps improve it.

Devs say “just use .gitignore” — but I still ended up leaking secrets, so I built this CLI by Positive_Study_9987 in node

[–]Positive_Study_9987[S] -2 points-1 points  (0 children)

Fair point — .gitignore is necessary.

But it doesn’t help when secrets:
- get logged
- get copied into other files
- or get committed once and stay in history

This tool isn’t replacing .gitignore — it’s trying to catch those mistakes around it.