Create table to store code commit comments

[bethanyaconnor]

This comes from the tech spec. I used the table name from the spec but there was a bit of discussion about it so let me know if there's a different name folks would prefer!

Links

Testing story

Deployment strategy

Follow-up work

Privacy

Security

Caching

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked

[bencodeorg]

I came to project_versions as a name for this as well before I noticed Suresh suggested the same thing in the tech spec :). I think probably worth renaming especially with the not obvious "metadatum" class name you get as the singular of "metadata"

[bencodeorg]

Sorry one other comment -- do you want storage_app_id to be unique?

[bethanyaconnor]

do you want storage_app_id to be unique?

Oh right probably not -- we want storage_app_id/version_id to be unique and we want a non-unique index on storage_app_id. I'll fix -- good catch!

[bethanyaconnor]

I came to project_versions as a name for this as well before I noticed Suresh suggested the same thing in the tech spec

Two votes for this is enough for me. I'll update

[bakerfranke]

LGTM. Good to know. Thanks.