Skip to content

What's new? exposure #13

@zanerock

Description

@zanerock

Something for the not-so-distance future: create automated with a combination of reference reading and tests. For continuing certification, you have to catch up with what's new. We automatically generate 'what's new' by saving the git hash of the last version read. In this way, we can detect when we need to generate a todo item for a user as well as show them exactly what has changed. Something like a bi-monthly review and annual testing would be a good baseline continuing certification level.

Clearly, this issue needs to be unpacked a bit.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions