Skip to content

Commit

Permalink
CONTRIBUTING: Document 'kick-ci' trick. (envoyproxy#4335)
Browse files Browse the repository at this point in the history
Risk Level: doc-only
Testing: n/a doc-only change
Docs Changes: CONTRIBUTING.md change.
Release Notes: n/a

Signed-off-by: Dan Noé <dpn@google.com>
  • Loading branch information
dnoe authored and htuch committed Sep 4, 2018
1 parent f13ef24 commit cddc732
Showing 1 changed file with 14 additions and 0 deletions.
14 changes: 14 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -214,3 +214,17 @@ git push origin -f

Note, that in general rewriting history in this way is a hinderance to the review process and this
should only be done to correct a DCO mistake.

## Triggering CI re-run without making changes

Sometimes CI test runs fail due to obvious resource problems or other issues
which are not related to your PR. It may be desirable to re-trigger CI without
making any code changes. Consider adding an alias into your `.gitconfig` file:

```
[alias]
kick-ci = !"git commit -s --allow-empty -m 'Kick CI' && git push"
```

Once you add this alias you can issue the command `git kick-ci` and the PR
will be sent back for a retest.

0 comments on commit cddc732

Please sign in to comment.