diff options
| author | Matt Rendina <rendinam@users.noreply.github.com> | 2019-01-07 16:01:52 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-01-07 16:01:52 -0500 |
| commit | 3dd293c4767ad012949c5fc5056cf5f9101dd840 (patch) | |
| tree | f5d482c5dba6f291cf238f72f69c15e610fbafe1 | |
| parent | 49b0532d241a1e8fa2a9a000e129554e8c476b6c (diff) | |
| download | jscu_refactor-3dd293c4767ad012949c5fc5056cf5f9101dd840.tar.gz | |
Update description of issue labeling behavior
| -rw-r--r-- | README.md | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -94,6 +94,8 @@ It has the following properties: #### Test Summary Issue Posts If test summaries are requested using the `post_test_summary` property of the JobConfig class as described above, each Jenkins job that produces one or more test errors or failures will result in a single new Github issue being posted to the project's repository. +If the label `testing` has been defined in the Github repository and a test summary issue ends up being generated for a job run, the issue that results will have the `testing` label applied. If a label with the name `testing` has not been defined on the repository, then the issue will be created without a label. + An example issue:  |