git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v4 4/5] doc: dissuade users from trying to ignore tracked files

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Jan 20, 2020, 17:33 UTC
Message-ID
<20200120173343.4102954-5-sandals@crustytoothpaste.net>
In-Reply-To
<20200120173343.4102954-1-sandals@crustytoothpaste.net>

It is quite common for users to want to ignore the changes to a file that Git tracks. Common scenarios for this case are IDE settings and configuration files, which should generally not be tracked and possibly generated from tracked files using a templating mechanism.

However, users learn about the assume-unchanged and skip-worktree bits and try to use them to do this anyway. This is problematic, because when these bits are set, many operations behave as the user expects, but they usually do not help when git checkout needs to replace a file.

There is no sensible behavior in this case, because sometimes the data is precious, such as certain configuration files, and sometimes it is irrelevant data that the user would be happy to discard.

Since this is not a supported configuration and users are prone to misuse the existing features for unintended purposes, causing general sadness and confusion, let's document the existing behavior and the pitfalls in the documentation for git update-index so that users know they should explore alternate solutions.

In addition, let's provide a recommended solution to dealing with the common case of configuration files, since there are well-known approaches used successfully in many environments.

Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
---

Peff, since I've adopted a significant portion of what you've said here, it's probably worth getting your sign-off on this patch.

 Documentation/git-update-index.txt | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
diff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt
index c7a6271daf..1489cb09a0 100644
--- a/Documentation/git-update-index.txt
+++ b/Documentation/git-update-index.txt
@@ -549,6 +549,22 @@ The untracked cache extension can be enabled by the
 `core.untrackedCache` configuration variable (see
 linkgit:git-config[1]).
 
+NOTES
+-----
+
+Users often try to use the assume-unchanged and skip-worktree bits
+to tell Git to ignore changes to files that are tracked.  This does not
+work as expected, since Git may still check working tree files against
+the index when performing certain operations.  In general, Git does not
+provide a way to ignore changes to tracked files, so alternate solutions
+are recommended.
+
+For example, if the file you want to change is some sort of config file,
+the repository can include a sample config file that can then be copied
+into the ignored name and modified.  The repository can even include a
+script to treat the sample file as a template, modifying and copying it
+automatically.
+
 SEE ALSO
 --------
 linkgit:git-config[1],
Previous: brian m. carlsonNext: Jeff King
Message 3 of 13 in “Documentation for common user misconceptions”
  1. 0/6 Documentation for common user misconceptionsbrian m. carlson, Jan 20, 2020
  2. 2/5 docs: expand on possible and recommended user config optionsbrian m. carlson, Jan 20, 2020
  3. 4/5 doc: dissuade users from trying to ignore tracked filesbrian m. carlson, Jan 20, 2020
  4. Jeff KingJan 20, 2020
  5. 1/5 doc: move author and committer information to git-commit(1)brian m. carlson, Jan 20, 2020
  6. Jeff KingJan 20, 2020
  7. brian m. carlsonJan 20, 2020
  8. Junio C HamanoJan 21, 2020
  9. Junio C HamanoJan 21, 2020
  10. 5/5 docs: mention when increasing http.postBuffer is valuablebrian m. carlson, Jan 20, 2020
  11. 3/5 doc: provide guidance on user.name formatbrian m. carlson, Jan 20, 2020
  12. Junio C HamanoJan 21, 2020
  13. Jeff KingJan 20, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.