Is git notes the intended way to add category-style information to a commit?

The answer to Can I add metadata to git commits? Or can I hide some tags in gitk mentions git notes as a way to add metadata to a git commit.

Is git notes, possibly taking advantage of its namespace functionality in case I want to add other types of notes, the best way to categorize commits? For example, I’d like to categorize commits into “refactoring”, “change-functionality”, “bug-fix”, “bug-introduce”, and be able to ask git to only list commits that are in certain categories.

  • Generate changelog for a semantically released package
  • Why is git still tracking files with extensions already added to .gitignore file
  • Reflecting Heroku push version within the app
  • Is there a better way to review your own changes instead of “git diff”
  • Trying to figure out the right approach to using submodules in git
  • Rolling back Visual Studio Extension to Earlier Version
  • How can I list all modified files by an author between a commit range but only with the last thing that happened to the file in Git?
  • Why does my git history look like a christmas tree?
  • How do I edit my staged file?
  • Errors in dumping a remote Git based SVN repository over HTTP
  • How to remove a file from the index in git?
  • SSH - Permission denied (cannot authenticate via CMD
  • One Solution collect form web for “Is git notes the intended way to add category-style information to a commit?”

    What you are proposing is quite similar to what the ruby-based gem “step-up” is doing, based on git notes.

    The great goal of this Gem is giving to developers an easy way to manage these notes.

    With a culture of notating all the relevant developments, its possible to retrieve a summary of a range of versions besides that specifying what kind of information will be retrieved.
    For example, imagine that you want to see all the features implemented in your application since the version v1.10.1 up to v2.0.0

    stepup notes --since v1.10.1 upto v2.0.0 --sections pre_deploy pos_deploy

    The result would be something like the following:

    Showing notes since v1.10.1 up to v2.0.0 (including notes of tags: v1.10.1, v1.10.2, v1.51.0, v2.0.0)
      - dependency of version v10 of project XYZ
      - it needed to rename the following file
        - config/environment_variables.yml.sample -> config/environment_variables.yml
      - rake articles:index
      - Reindex articles
        - rake articles:index
      - rake db:seed
      - rake categories:reload

    ranged_notes.rb will define functions to get all the relevant commits, based on their notes.
    git.rb contains the actual git notes commands.

    Git Baby is a git and github fan, let's start git clone.