From 4f43977d433ae27b6532239bf4f2a45f64d52027 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ot=C3=A1vio=20Fernandes?= Date: Tue, 22 Mar 2022 19:35:41 +0100 Subject: [PATCH] Update ships/0031-shipwright-trigger.md Co-authored-by: Gabe Montero --- ships/0031-shipwright-trigger.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ships/0031-shipwright-trigger.md b/ships/0031-shipwright-trigger.md index dd0580d..93ed885 100644 --- a/ships/0031-shipwright-trigger.md +++ b/ships/0031-shipwright-trigger.md @@ -9,7 +9,7 @@ This enhancement proposal describes how Shipwright will react to: - WebHooks: Handles WebHook requests from Git service providers, like GitHub, in order to activate a Build - Tekton Pipelines: Integration between Tekton Pipelines and Shipwright, Builds will be triggered when a given Pipeline has reach the desired status - Tekton [Custom-Tasks](https://github.com/tektoncd/community/blob/main/teps/0002-custom-tasks.md) (Run): A new Custom Task will allow users to call out Shipwright Builds directly from Pipelines -Images: Integration with the new Shipwright [Image project](https://github.com/shipwright-io/image), changes to any Images managed by that project that serve as input into a Shipwright Build will initiate new BuildRuns when any of those images change. +- Images: Integration with the new Shipwright [Image project](https://github.com/shipwright-io/image), changes to any Images managed by that project that serve as input into a Shipwright Build will initiate new BuildRuns when any of those images change. # Motivation