about summary refs log tree commit diff homepage
path: root/.github
diff options
context:
space:
mode:
authorMartin Nowack <m.nowack@imperial.ac.uk>2020-12-02 10:31:07 +0000
committerMartinNowack <2443641+MartinNowack@users.noreply.github.com>2020-12-02 15:11:39 +0000
commitc51ffcd377097ee80ec9b0d6f07f8ea583a5aa1d (patch)
tree13b886cf29391ac8c6fcd466898d221259f92439 /.github
parent4411278ed77bda7d51edd0cbae160b1cdaa0e7b9 (diff)
downloadklee-c51ffcd377097ee80ec9b0d6f07f8ea583a5aa1d.tar.gz
Use Github Actions as default CI
Diffstat (limited to '.github')
-rw-r--r--.github/pull_request_template.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index c69cd241..86cf67e9 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -8,5 +8,5 @@ To help expedite the review please ensure the following, by adding an "x" for ea
 - [ ] Each commit has a meaningful message documenting what it does.
 - [ ] The code is commented.  In particular, newly added classes and functions should be documented.
 - [ ] The patch is formatted via  [clang-format](https://clang.llvm.org/docs/ClangFormat.html) (see also [git-clang-format](https://raw.githubusercontent.com/llvm/llvm-project/master/clang/tools/clang-format/git-clang-format) for Git integration).  Please only format the patch itself and code surrounding the patch, not entire files.  Divergences from clang-formatting are only rarely accepted, and only if they clearly improve code readability.
-- [ ] Add test cases exercising the code you added or modified.  We expect [system and/or unit test cases](https://klee.github.io/docs/developers-guide/#regression-testing-framework) for all non-trivial changes.  After you submit your PR, you will be able to see a [Codecov report](https://docs.codecov.io/docs/pull-request-comments) telling you which parts of your patch are not covered by the regression test suite.  You will also be able to see if the Travis CI and Cirrus CI tests have passed.  If they don't, you should examine the failures and address them before the PR can be reviewed. 
+- [ ] Add test cases exercising the code you added or modified.  We expect [system and/or unit test cases](https://klee.github.io/docs/developers-guide/#regression-testing-framework) for all non-trivial changes.  After you submit your PR, you will be able to see a [Codecov report](https://docs.codecov.io/docs/pull-request-comments) telling you which parts of your patch are not covered by the regression test suite.  You will also be able to see if the Github Actions CI and Cirrus CI tests have passed.  If they don't, you should examine the failures and address them before the PR can be reviewed. 
 - [ ] Spellcheck all messages added to the codebase, all comments, as well as commit messages.