{"push_id":4086506260,"size":1,"distinct_size":1,"ref":"refs/heads/follow_the_resources","head":"ef5c635d11f154654de6890aa81fda65c51e1105","before":"10b6f5bb70bcad8489208425e71bf62a506af029","commits":[{"sha":"ef5c635d11f154654de6890aa81fda65c51e1105","author":{"name":"Christie Wilson","email":"2bc232eb503bd255b6ba880733f66f1ba6cd2e57@gmail.com"},"message":"Use the same logic to resolve spec vs ref in Pipelines + Tasks\n\nIn #1324 we updated PipelineRuns to allow for embedding ResourceSpecs in\nPipelineRuns. This commit makes it so that the logic for resolving (i.e.\ndeciding if PipelineResources are specified by Spec or Ref) is shared by\nPipelineRuns + TaskRuns. This is done by making it so that the \"binding\"\nuses the same type underneath. The only reason they can't be the exact\nsame type is that TaskRuns additionally need the \"path\" attribute, which\nis actually only used for PVC copying, which will be removed in #1284,\nand then we should be able to remove paths entirely and the type can be\nthe same.\n\nAlso added some additional comments around the use of `SelfLink`, and\nmade sure it was well covered in the reconciler test.","distinct":true,"url":"https://api.github.com/repos/bobcatfish/pipeline/commits/ef5c635d11f154654de6890aa81fda65c51e1105"}]}
{"actor":{"display_login":"bobcatfish"}}