kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity

Add retriggering CI section

Browse Source 
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 <guillaume.derouville@gmail.com>
This commit is contained in:
guillaume 2022-01-12 01:07:51 +01:00
parent e43f6db4b1
commit 988bf902c2
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
CONTRIBUTING.md
View File

@ -127,3 +127,17 @@ Then from the repository root:
```console ```console
markdownlint -c .markdownlint.yaml docs/**/*.md 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 <your-fork> <Branch> --force
```