{"push_id":3012774370,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"9ae06881c4027fa20719db8bdb85f846e0fcccfc","before":"b1678bf3fffe4bed7485a18281f342f2d4b68af6","commits":[{"sha":"9ae06881c4027fa20719db8bdb85f846e0fcccfc","author":{"name":"Aaron Prindle","email":"ab7d38f1b9959aa5832ffbabd6f0beb9abebfb47@google.com"},"message":"TaskRun Validation - Controller Side\n\nWhat is the problem being solved?\nFixes #188, TaskRun Validation - Controller Side.  This PR adds additional TaskRun validation to the TaskRun controller which checks that referenced Params and Resources exist and that they are bound properly from the Task.\n\nWhy is this the best approach?\nThis approach follows the style and convention for a similar issues, #162, PipelineRun validation.\n\nWhat other approaches did you consider?\nN/A\n\nWhat side effects will this approach have?\nIt is possible that some demo/sample yaml which use to execute will no longer work as we have this additional validation.\n\nWhat future work remains to be done?\nFor the TaskRun controller, I believe that this validation is sufficient.  In the future we should extend validation to all of our primitive types, especially PipelineResource.","distinct":true,"url":"https://api.github.com/repos/knative/build-pipeline/commits/9ae06881c4027fa20719db8bdb85f846e0fcccfc"}]}
{"actor":{"display_login":"knative-prow-robot"}}