On Mon, May 30, 2016 at 08:58:08PM +0300, Kirill Likhodedov wrote: > Is it possible to add custom metadata to Git commit object? Such > metadata should be ignored by Git commands, but could be used by a > 3-party tool which knows the format and knows where to look.
Yes. The recommended place to stick this is in a "trailer" at the bottom of the commit message, like: Rename-detection-hint: foo.java -> bar.java or whatever scheme is useful to your tool. > I assume that this should be possible, given that Git objects are > actually patches, and patches can contain additional details. But can > this be done with the help of Git commands? Git objects aren't actually patches. Try: git cat-file commit HEAD to see what an actual commit object looks like. You will see that there are user-invisible headers before the commit message, too, but we do not usually recommend people to add new headers here, as their semantics would be unclear to git. For example, when rebasing such a commit, should the header be preserved or not? It depends on its meaning. Whereas commit messages are always preserved. > There are git-notes, which could be used for the purpose, but they are > visible to the user via standard Git command, and could be used by the > user for other purposes, so they are not very suitable for the task. Notes would work for this, too, but their main advantage is that they can be created _after_ a commit has already been made (whereas anything in the commit object itself will influence its sha1 id). -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
