gh-mirrors/firefly-iii
1
0
Fork 0
mirror of https://github.com/firefly-iii/firefly-iii.git synced 2025-12-10 05:11:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

Improve automated reply message for debug info

Browse Source 
Signed-off-by: James Cole <james@firefly-iii.org>
This commit is contained in:
James Cole
2025-11-11 09:37:30 +01:00
committed by GitHub
parent 3fd31bdf70
commit 49b42538f5
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.github/workflows/issues-reply-old-versions.yml vendored
View File

@@ -56,7 +56,7 @@ jobs:
You triggered an automated reply, because it looks like you didn't include the output from the \`/debug\` page. Would you be so kind as to do that? It helps the developers debug your issue more easily. You triggered an automated reply, because it looks like you didn't include the output from the \`/debug\` page. Would you be so kind as to do that? It helps the developers debug your issue more easily.
If you did include debug information, and this message is wrong, my apologies for the intrusion." If you *did* include debug information or of if the debug information isn't relevant (or even reachable), my apologies for the intrusion."
gh issue comment "$NUMBER" --body "$MESSAGE" gh issue comment "$NUMBER" --body "$MESSAGE"
echo "Triggered on first test" echo "Triggered on first test"
@@ -71,7 +71,7 @@ jobs:
Thank you for running the latest version of Firefly III (or the data importer). You triggered an automated reply, because it looks like you didn't include the output from the \`/debug\` page. Would you be so kind as to do that? It helps the developers debug your issue more easily. Thank you for running the latest version of Firefly III (or the data importer). You triggered an automated reply, because it looks like you didn't include the output from the \`/debug\` page. Would you be so kind as to do that? It helps the developers debug your issue more easily.
If you did include debug information, and this message is wrong, my apologies for the intrusion." If you *did* include debug information or of if the debug information isn't relevant (or even reachable), my apologies for the intrusion."
gh issue comment "$NUMBER" --body "$MESSAGE" gh issue comment "$NUMBER" --body "$MESSAGE"
echo "Triggered on second test" echo "Triggered on second test"