.gitignore broken, .env leaking. #167032
Replies: 3 comments
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Even worse, I just noticed that the .env file doesn't even show up in the source control list. |
Beta Was this translation helpful? Give feedback.
-
bro, try it from the terminal. Try: git status and see if the .env appears. And see if the .gitignore directory is in the same path. if with git status no seeing, then is working, just commit. 🥱 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
I don't know if this applies to every form of codespaces, I only tested on github.dev on a regular repo, but when I use
Commit & Push
, it doesn't strip files that follow the .gitignore.Steps to reproduce:
Screen.Recording.2025-07-22.at.00.39.14.mov
Beta Was this translation helpful? Give feedback.
All reactions