You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Github Token that uses for posting the comments in Pull Requests
51
52
github-token: ${{ secrets.GITHUB_TOKEN }}
53
+
# Optional extra section comments to publish alongside the summary table
54
+
# Supported values: new, flaky, retry, all
55
+
# Default: hidden
56
+
sections: |
57
+
new
58
+
flaky
52
59
```
53
60
54
61
If everything is set up correctly and required reports data is present, the Action will post a comment with Allure Report summary to your Pull Request, like this:
@@ -59,6 +66,33 @@ If everything is set up correctly and required reports data is present, the Acti
59
66
60
67
The action utilizes Allure 3 Runtime configuration file (`allurerc.js` or `allurerc.mjs`) and use `output` field as a path, where it should search for the generated reports.
61
68
69
+
### Comment sections
70
+
71
+
By default, the action posts the summary table only. You can enable additional section comments in the Pull Request with the `sections` input:
72
+
73
+
```yaml
74
+
with:
75
+
sections: |
76
+
new
77
+
flaky
78
+
```
79
+
80
+
Supported values:
81
+
82
+
- `new`
83
+
- `flaky`
84
+
- `retry`
85
+
- `all`
86
+
87
+
The input accepts comma-separated or newline-separated values.
88
+
89
+
When enabled:
90
+
91
+
- each section is published as a separate comment
92
+
- section comments are wrapped in a collapsible `<details>` block
93
+
- comments are updated on the next run using dedicated markers
94
+
- oversized test lists are truncated and include a `More` link to the filtered remote report when available
95
+
62
96
### Remote reports
63
97
64
98
If you want to be able to open remote reports automatically hosted on Allure Service, provide `allureService` configuration to the `allurerc.js` configuration file:
0 commit comments