From 988bf902c2c7df0782c0827cb50ceb798c329676 Mon Sep 17 00:00:00 2001 From: guillaume Date: Wed, 12 Jan 2022 01:07:51 +0100 Subject: [PATCH] Add retriggering CI section Several contributors asked us how to retrigger the CI. This PR adds a section to contributing.md showing an example Pairs: @gerhard, @slumbering Signed-off-by: guillaume --- CONTRIBUTING.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a0bbd3fe..f2a2c1d7 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -127,3 +127,17 @@ Then from the repository root: ```console markdownlint -c .markdownlint.yaml docs/**/*.md ``` + +### How to retrigger a Github Action workflow? + +There isn't a button that Dagger contributors can click in their fork of Dagger that will trigger a GitHub Action workflow run. See issue [#1669](https://github.com/dagger/dagger/issues/1169) for more context. + +The current workaround is to force push to your fork: + +```bash +➜ # Apply a small change to a comment +➜ git add --all +➜ make lint # Make sure that the linter is happy :) +➜ git commit --signoff --amend +➜ git push --force +```