Add feature to stop tracking files while keeping them in the index

Add feature to stop tracking files while keeping them in the index

[Viet Nguyen]

Hello everyone,

Currently, a file can be either tracked or untracked. So, I propose we
add a feature to stop tracking files while keeping them in the index.

Example scenario:
- A developer would like to add some configuration files with example
values, e.g. DB_PASSWORD=changeme. But in the future he also want to
update those files and to notify the others with conflicts.

Best regards,

Viet Nguyen

Re: Add feature to stop tracking files while keeping them in the index

[Igor Djordjevic]

Hi Viet,

On 20/11/2017 10:52, Viet Nguyen wrote:
> Currently, a file can be either tracked or untracked. So, I propose we
> add a feature to stop tracking files while keeping them in the index.
> 
> Example scenario:
> - A developer would like to add some configuration files with example
> values, e.g. DB_PASSWORD=changeme. But in the future he also want to
> update those files and to notify the others with conflicts.

If I`m understanding you correctly, what you want should already be 
possible through `git update-index --[no-]skip-worktree`[1].

Regards, Buga

[1] https://git-scm.com/docs/git-update-index#git-update-index---no-skip-worktree

Re: Add feature to stop tracking files while keeping them in the index

[Viet Nguyen]

Hi Igor,

On November 20, 2017 at 7:15:00 PM, Igor Djordjevic
(igor.d.djordjevic@gmail.com) wrote:
> Hi Viet,
>
> On 20/11/2017 10:52, Viet Nguyen wrote:
> > Currently, a file can be either tracked or untracked. So, I propose we
> > add a feature to stop tracking files while keeping them in the index.
> >
> > Example scenario:
> > - A developer would like to add some configuration files with example
> > values, e.g. DB_PASSWORD=changeme. But in the future he also want to
> > update those files and to notify the others with conflicts.
>
> If I`m understanding you correctly, what you want should already be
> possible through `git update-index --[no-]skip-worktree`[1].
>
> Regards, Buga
>
> [1] https://git-scm.com/docs/git-update-index#git-update-index---no-skip-worktree
>

We are currently using git-update-index in a client hook, but found it
a little tedious because sometime we forget to configure the hooks
correctly and it just stop working. So I am thinking that it would be
a lot better if we can store it somewhere in the shared repository, so
the other developers could ignore the fact that some files in our
project are special and treat them just like the regular files.

Best regards,

Viet