Every time a user manually saves a design, the version description is set to «User Saved». This might as well just be a random, non-descriptive string.
Why not provide a brief summary of the last action a user performed (or a list of actions). It'd be much more useful to say «created user parameters» or «created sketch».
Given that this is (more or less) version control, it might be good to have some sort of guideline to writing good commit messages like
Short (50 chars or less) summary of changes
More detailed explanatory text, if necessary. Wrap it to
about 72 characters or so. In some contexts, the first
line is treated as the subject of an email and the rest of
the text as the body. The blank line separating the
summary from the body is critical (unless you omit the body
entirely); tools like rebase can get confused if you run
the two together.
Further paragraphs come after blank lines.
- Bullet points are okay, too
- Typically a hyphen or asterisk is used for the bullet,
preceded by a single space, with blank lines in
between, but conventions vary here
To that end, it'd also be great to have the description have space for a multi-line commit message rather than just a short set of words
