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
Copy file name to clipboardExpand all lines: README.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,17 @@ Please note: The parsed report file will also be committed and pushed if it chan
41
41
If you do not enable **push_badge** you'll need extra steps in your workflow to commit and push the file into the repository.
42
42
Please have a look at the inputs for all configuration options.
43
43
44
+
# Troubleshooting
45
+
46
+
## Commit by action triggers another action run
47
+
As reported by [MikeDevresse](https://github.com/MikeDevresse) in [this issue](https://github.com/timkrase/phpunit-coverage-badge/issues/7), it might be possible that the commit by the Github action triggers a subsequent action run. Adding a specific tag to the actions github action and then checking for the existance of this tag can be used as a workaround (example is a slightly modified version of the one given by MikeDevresse in the issue):
0 commit comments