I have moved all the QA logic into the pipeline. Because of this it is would be better to use the QA status table. It now contains a column called messages, which is a JSON encoded list of QA messages to show. Each entry in the list is a message, that may contain HTML that should be displayed as the QA failure message.
I have moved all the QA logic into the pipeline. Because of this it is would be better to use the QA status table. It now contains a column called messages, which is a JSON encoded list of QA messages to show. Each entry in the list is a message, that may contain HTML that should be displayed as the QA failure message.