QA Shepherd project developer notes
User stories
- As an operator and developer, I want to read in the log files the detailed reasons that the shepherd took a particular action, so that debugging the tool is easier.
devspeak: the log should record both the current state of the change sources and the state transitions that the shepherd executes based on said current state.
- As a user, I want to read an HTML report that tells me whether my branch has been promoted from QA to production, so I do not have to rely on