IntenseFinance/firefly-iii
3
0
Fork 0
mirror of https://github.com/firefly-iii/firefly-iii.git synced 2025-01-10 08:03:36 -06:00
Code Issues Packages Projects Releases Wiki Activity

Update label-actions.yml

Browse Source 
Signed-off-by: James Cole <james@firefly-iii.org>
This commit is contained in:
James Cole 2024-01-08 20:20:22 +01:00 committed by GitHub
parent 2c3f032a2b
commit 6a9b4f4d55
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 29 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
.github/label-actions.yml vendored
View File

@ -35,3 +35,32 @@ triage:
This issue has been marked as being in triage. The root cause is not known yet, or the issue needs more investigation. You can help by sharing debug information (from `/debug`) if you also have this issue or when you haven't already done so.
Thank you for your contributions.
needs-moar-debug:
issues:
comment: |
Hi there! This is an automatic reply. `Share and enjoy`
To learn more about this issue, please share the output of the `/debug` page of your Firefly III installation.
If this page is no available due to the issue you have, please make sure you share at least:
1. Firefly III version
2. Docker, self-hosted, or hosted by a third party?
3. Operating system and browser
Thank you for your contributions.
needs-moar-logs:
issues:
comment: |
Hi there! This is an automatic reply. `Share and enjoy`
To learn more about this issue, please share the relevant log files from your Firefly III or data importer installation.
The relevant instructions can be found in the documentation: [How to debug Firefly III?](https://docs.firefly-iii.org/how-to/general/debug/) Once debug mode is activated per these instructions, you can repeat your action and find the logs, depending on your method of installation. All is explained on the page.
Please share the relevant log lines in your issue, either inline or as an attachment. If you feel the logs contain sensitive information, you may also send them to [james@firefly-iii.org](mailto:james@firefly-iii.org). Without these logs, it may not be possible to properly investigate this issue.
Thank you for your contributions.