Can git track files, but not show them as updated?

Question

Use case: we have some project metadata files that we want to track, but rarely (if ever), although they are constantly updated locally (different users have different project paths). In normal scenarios, no one should ever commit these files unless explicitly required.

Git ignore is used for irreproducible files.

Is there a similar function for git to ignore tracked files ? Is there a way that I can change in the central repo and it will be displayed to all users?

Answer 1

Is there a way that I can change in the central repo and it will be displayed to all users?

Not in the general (distributed) context: no hook or process of any type can be “modified” in a central location and selected by all distributed downstream repositories.

If your user created his repo after the central template , then some kind of default hook can refer to the central script (i.e. the script is accessible to all users on the shared disk if we are talking about users on the same network).

---

adymitruk answer states that the development branch is used, therefore, without making particular changes to the “public” branch (that is, the branch that is pressed / pulled).
This is good and good, but:

• This is not an automatic process (mandatory for all repositions), but an action taken by each developer individually (or not accepted because they forgot)
• this includes sorting the commits that you do not want to publish from those you need to publish, which you would do anyway with the development branch, except that the developer must take an additional step of remembering that any changes to these files should not be merged into a public branch. Ever. (assuming he really took the time to isolate these specific changes in a separate commit!).

---

Better use a filter driver (which is declared in the .gitattributes file and can be distributed via the clone ) with:

• a smudge script:

  • the ability to recognize the contents of your metadata files
  • saving contents at the checkout

• a clean script:

  • the ability to recognize the contents of your metadata files
  • decide whether changes should be made or not.
  • restore the original content of these metadata files when committing

Answer 2

 $ git update-index --assume-unchanged <filename> 

This only works locally.

Answer 3

Use development branches. Accept your specific changes in your environment. Back merges with our strategy. Now these changes will never be transferred to the public division. Other answers lack the ability to use development branches.