From 3dd293c4767ad012949c5fc5056cf5f9101dd840 Mon Sep 17 00:00:00 2001 From: Matt Rendina Date: Mon, 7 Jan 2019 16:01:52 -0500 Subject: Update description of issue labeling behavior --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index aa4675e..27b119c 100644 --- a/README.md +++ b/README.md @@ -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: ![issue_image](doc/test_summary_issue.png "Example issue") -- cgit