You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not 100% sure if this is an issue with gitignore or my bad powershell skills, but I thought I would just add this here because maybe it's an easy fix.
When I tried using the gitignore util with the powershell command gitignore python >> .gitignore the command produced the full python gitignore template but the template didn't seem to be recognised by git. One of the excluded directories in the template is /build yet whenever I did a git add . on a fresh repository the /build directory was always included.
However, if I copied the template from gitignore.io to a new .gitignore file then there was no issue and the build folder wasn't staged. So I wonder if this is a text encoding issue, because when I copy and pasted the .gitignore file works but when piped it doesn't. I also noticed that the command line tool on gitignore.io adds -Encoding ascii to their command
I'm not 100% sure if this is an issue with gitignore or my bad powershell skills, but I thought I would just add this here because maybe it's an easy fix.
When I tried using the
gitignore
util with the powershell commandgitignore python >> .gitignore
the command produced the full python gitignore template but the template didn't seem to be recognised by git. One of the excluded directories in the template is/build
yet whenever I did agit add .
on a fresh repository the/build
directory was always included.However, if I copied the template from gitignore.io to a new
.gitignore
file then there was no issue and thebuild
folder wasn't staged. So I wonder if this is a text encoding issue, because when I copy and pasted the .gitignore file works but when piped it doesn't. I also noticed that the command line tool on gitignore.io adds-Encoding ascii
to their commandHere are the
.gitignore
files that I generated.not_working.txt
working.txt
The text was updated successfully, but these errors were encountered: