Re: [Feature Request] Option to make .git not read-only in cloned repos

From: Albert Vaca Cintora <albertvaka@gmail.com>
Date: Aug 31, 2019, 20:40 UTC
Message-ID: <CAAQViEufHT70-c17hdPqFh4HxB1Wy1dF6huF88P2-n+LWkhamQ@mail.gmail.com>
In-Reply-To: <xmqqmufqxxof.fsf@gitster-ct.c.googlers.com>

On Fri, Aug 30, 2019 at 9:25 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 16 quoted lines

>
> But between these two:
>
>         $ git clone --no-read-only-file-in-git https://github.com/foo/bar
>         ...sightsee...
>         $ rm -r bar
>
> to avoid "f" in "rm -r", vs.
>
>         $ git clone https://github.com/foo/bar
>         ...sightsee...
>         $ rm -rf bar
>
> to clone a repository you only have a tentive interest in just like
> any other more permanent repositories, I am not sure how the former
> is preferrable.

I would permanently enable --no-read-only-file-in-git for all newly cloned repositories (via an alias, or .gitconfig if possible), so there would be no need to type it every time.