开发者

Git hooks for metadata storage/retrieval

开发者 https://www.devze.com 2022-12-21 03:53 出处:网络
One of git\'s unavoidable quirks is its inability to store and retrieve metadata about a file. For example, on the mac, labels are stored wi开发者_如何学编程th \"extended attributes\" (accessible with

One of git's unavoidable quirks is its inability to store and retrieve metadata about a file. For example, on the mac, labels are stored wi开发者_如何学编程th "extended attributes" (accessible with xattr), and any checkout/reset/merge/pull command will erase those attributes if the file is affected by the checkout.

I've looked around to see if someone has written metadata-saving scripts already, but I came up dry.

So what I'd like to do is use Git's hook system to:

  1. Read extended attributes when files are committed,
  2. Write the attributes to a file stored in the repository that also gets committed,
  3. Apply the extended attributes to files that are modified in a merge/checkout/reset.

Which of the hooks should I use? Are post-receive and pre-commit all that I need? Can pre-commit also add a file to the commit (i.e., after writing the new attributes)?


The gibak tool uses pre-commit and post-checkout to let its ometastore tool save/restore metadata (optionally including xattrs).

You do not want post-receive. It is run on the remote end of pushes. It runs for bare repositories, so it has no business trying to update any files from the contents of a pushed commit. Do it in post-checkout where you know you will have a working tree available.


metastore is able to save and restore file metadata, storing it in a separate file (which you can include in your commits)

0

精彩评论

暂无评论...
验证码 换一张
取 消