comment fields create multiple-source-of-truth and churn

[seanmakesgames]

problem

any content that could be added into the 'comment' field at this time would be less accurate than our source control git blame and would get stale very quickly. It's an easy place to introduce drag and increase maintenance costs.

context

We should be programmatically enforcing no comment field.

Originally posted by @seanmakesgames in #30 (comment)

[kaj-se]

@hmdunce and I could create a script for that. It would check whether the field is set and remove it if necessary.

But how about the of generating the information for the Comment tags of the glyph structure based on the information in the repo and then adding it to the tags? The update process would run automatically when a merge with the repo takes place.

[seanmakesgames]

@hmdunce and I could create a script for that. It would check whether the field is set and remove it if necessary.

But how about the of generating the information for the Comment tags of the glyph structure based on the information in the repo and then adding it to the tags? The update process would run automatically when a merge with the repo takes place.

#30 (comment)

Look up 'single source of truth' for more info on what this is about.