11–20 of 147 posts
https://alchemists.io/articles/git_trailers
These are key-value structures data that can be included on a commit when it is created. These are used by some systems for attaching metadata. For example, Gerrit uses this for attaching its Change-Id.
Another little-known feature is git trailers: https://alchemists.io/articles/git_trailers These are key-value structures data that can be included on a commit when it is created. These are used by some systems for attaching metadata. For example, Gerrit uses this for attaching its Change-Id.
https://www.postgresql.org/docs/17/sql-comment.html
This allows you to attach text to various database objects in PostgreSQL.
I wish PostgreSQL had a feature that was more like structured key-value database object metadata that could be edited.
I've been using git for probably 10 years and I didn't know git notes existed. Cool! > Here is a plea for all forges: make code review metadata available offline, inside git. I think this will fall on deaf ears as far as commercial forges like GitHub go, since as you yourself observe: > But much of the value of git repos ends up locked into forges, like GitHub. For-profit enterprises are not generally excited about c…
You have to start a new service that offers that feature as one of its differentiators, then the competitors might add it (back) to catch up.
Git notes are only cool if you frequently add text to a commit after the commit has happened and visible to others. The Acked-By and mailing list discussion link examples don't seem to be good examples. Both of these are likely already known when the commit is made. And git commit message basically can have an unlimited length, so you could very well copy all the discussions about the commit that happened on a forge…
Earlier quoted context omitted.
You have to start a new service that offers that feature as one of its differentiators, then the competitors might add it (back) to catch up.
any reason why Forgejo/Codeberg couldn't/wouldn't adopt this?
I bet it already exists, but what about an issue tracker in plain text maintained by git itself?
I have an issue tracker file that can be added to a project. While it's technically plain text, the interface for the file ensures that a format is used, and the format ensures that changes reflect only a single ticket.
Just as long as no one edits the file using a different program, it will work just fine.
Don't think anyone uses it, though.
I bet it already exists, but what about an issue tracker in plain text maintained by git itself?
Another little-known feature is git trailers: https://alchemists.io/articles/git_trailers These are key-value structures data that can be included on a commit when it is created. These are used by some systems for attaching metadata. For example, Gerrit uses this for attaching its Change-Id.
Also supported by Forgejo since version 10 (released in January of this year): https://forgejo.org/2025-01-release-v10-0/#new-features https://codeberg.org/forgejo/forgejo/pulls/4753