Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CONTRIBUTING: Document 'kick-ci' trick. #4335

Merged
merged 1 commit into from
Sep 4, 2018
Merged

CONTRIBUTING: Document 'kick-ci' trick. #4335

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
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.