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
This GitHub Action can produce fancy and more meaningful discord messages for your commits.
3
3
<br>It includes Test results and coverage.
4
4
@@ -7,7 +7,7 @@ This currently works only for Maven projects.
7
7
For Test Results and Coverage Reports you will need to use one of the following Maven plugins:
8
8
*`maven-surefire`
9
9
*`maven-failsafe`
10
-
*'jacoco'
10
+
*`jacoco`
11
11
12
12
## Inputs
13
13
@@ -18,7 +18,34 @@ For Test Results and Coverage Reports you will need to use one of the following
18
18
**Required** Now your Discord webhook token, it's the second part of the url.
19
19
20
20
## Screenshots
21
-
TODO
21
+
The standard webhook from GitHub to Discord just dumps the commit messages right into your chat, this is fine but sometimes you just want some extra information. Did the commit introduce any new issues? Did it even compile successfully? That's what this Action is for.<br>
* Removed the obnoxious author name and image at the top (may be a toggle in the future)
31
+
* The branch is now clearly visible "Slimefun4:master" -> "Slimefun4 (master)"
32
+
* The repository is now referred to by its full name, including the repository owner
33
+
* The embed now includes a timestamp (it is actually the timestamp of the commit, not just the current date of when the webhook was sent)
34
+
* Commit messages have slightly shorter limits and the committer is now better distinguishable from the commit message "Reduced technical debt - TheBusyBiscuit" -> "Reduced technical debt (@TheBusyBiscuit)"
35
+
* Includes test results, passes will be prepended with a green circle, skips with yellow and failures with red.
36
+
* It will also list the exact tests which failed (max of 4, then it will crop them)
37
+
* An estimated test coverage is provided if you use the `jacoco` maven plugin.
38
+
* Dynamic embed color changes
22
39
23
-
## Example workflow
24
-
TODO
40
+
#### Dynamic Coloring
41
+
The color of the embed changes depending on the compiler and test results. Here's a breakdown:
42
+
43
+
| Color | Description |
44
+
| ----- | ----------- |
45
+
| red | The build has failed. |
46
+
| orange | The build was successful but some tests failed. |
47
+
| yellow | The build was successful, no tests failed but some were skipped. |
48
+
| green | The build was successful, no tests failed and none were skipped. |
0 commit comments