Add a default VersioncontrolTag::getMessage(), that backends can override to provide tag annotations

yep, just what i was looking for. commushing. now we can sort out what the actual implementation should look like in vc_git land.

I am really late here, but I would say we should follow the same pattern we use in operations. That means adding a data member(this sounds like we really need to review code) for the message, and a column to the versioncontrol_labels table, to actually store it, so we can access it from places like views(IMHO we do not want to call repositories for it).

i don't want a data member. i want separate, backend-specific tables that can be joined in.

the data member is ok on operations b/c it's pretty well established across vcs types that you'll have a commit message. tags are not nearly so standardized, so i'd rather not put something in the generic table which is going to be used different ways, if at all, by different backends.

Make sense. Opening #1666622: Support tag messages and re-closing this.