git:notes

Git notes provide a non-invasive way to attach metadata to commits without modifying object SHAs or altering commit hashes, enabling teams to record review status, test results, and audit information.

Yes, you can share git notes across repositories by pushing and fetching refs/notes/* to share annotations across remotes, using named notes refs and namespaces to keep them scoped and discoverable.

The best way to track code review status without amending commits is using namespaced git notes, which allow you to record approvals and annotations in separate notes refs for reviews, testing, and audits without changing object SHAs.

Git notes can be preserved during rebase and amend operations by configuring rewrite settings like notes.rewrite.rebase, ensuring your annotations remain attached to commits after history modifications.

To display git notes from different namespaces, configure options like notes.displayRef for preservation and display, allowing you to view annotations across separate notes refs for reviews, testing, and audits.

Yes, you can perform bulk operations to annotate multiple git commits by author or range, attaching metadata like test results or audit information across multiple objects without rewriting history.