Hi Duy,
> This is a general problem to new files, not .gitignore alone. Can we
The difference, to me, is that a ".gitignore" file is not part of what
I'm developing. It's an artifact for git configuration. While a
.gitignore file is not always pushed to the repository, I imagine that
in most situ
On Thu, Feb 9, 2017 at 2:05 AM, Thangalin wrote:
> I frequently forget to add .gitignore files when creating new .gitignore
> files.
>
> I'd like to request a command-line option to always add .gitignore
> files (or, more generally, always add files that match a given file
> specification).
>
> R
> I am tempted to say that there should be a way to somehow forbid use
> of the "-m" option to "git commit" by default, until the user gains
> more familiarity with use of Git.
Since I am using git, I am tempted to say that "git commit -m" should be
abolished. If I tell somebody how to use git, I
Thangalin writes:
> I frequently forget to add .gitignore files when creating new .gitignore
> files.
>
> I'd like to request a command-line option to always add .gitignore
> files (or, more generally, always add files that match a given file
> specification).
That is essentially what "Untracke
I frequently forget to add .gitignore files when creating new .gitignore files.
I'd like to request a command-line option to always add .gitignore
files (or, more generally, always add files that match a given file
specification).
Replicate
0. git init ...
1. echo "*.bak" >> .gitignore
2. touch
5 matches
Mail list logo
