Closed cmc333333 closed 5 years ago
In discussion so far, we think this is more of a pre-processing step that could be done in any number of templating systems. We could also provide a hook for CM to invoke the user's own pre-processing step at the appropriate time.
Two year old discussion. Closing for inactivity. Feel free to reopen as appropriate!
Consider tools like Gemnasium, Quantified Code, and Travis -- each covers some component of the compliance process. However, adding a verification for each requires adding a unique URL (i.e. pointing to the project page within Gemnasium, QC, Travis). It'd be handy if we could define component docs for each of these tools once and re-use them across projects, but there's no way to template that URL/project id/etc. One potential approach would be to add something to the
opencontrol.yaml
file: