Scan AUX into zotero imports nothing with the Biber / BibLaTeX project #10517
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: 'Manage issues and nag about debug logs' | |
| on: | |
| issues: | |
| types: [opened, edited, closed, reopened] | |
| issue_comment: | |
| types: [created, edited, closed] | |
| jobs: | |
| nag: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: retorquere/label-gun@main | |
| with: | |
| token: ${{ github.token }} | |
| label.exempt: question | |
| label.awaiting: awaiting-user-feedback | |
| label.log-required: needs-debug-log | |
| label.reopened: reopened | |
| log-id: "([A-Z0-9]{8}(-refs)?-(apse|euc))|([A-Z0-9]{8}-[^-]+)" | |
| message.log-required: | | |
| Hello there @{{username}}, | |
| Hope you're doing well! `@retorquere` is here to help you get the most out of your experience with Better BibTeX. To make sure he can assist you effectively, he kindly asks for your cooperation in providing a debug log – it's like giving him the key to understanding and solving the puzzle! | |
| Getting your debug log is a breeze and will save us both time in getting your problem resolved or the new feature you'd like implemented. Trust me, it's way quicker than discussing why it's important. :smiley: | |
| **How to Share Your Debug Log:** | |
| 1. If the issue involves specific references, citekey generation, or exports, just right-click on the relevant item(s) and choose "Better BibTeX -> Submit Better BibTeX debug log" from the menu. | |
| 2. For other issues, follow these simple steps: | |
| * Restart Zotero with debugging enabled (Help -> Debug Output Logging -> Restart with logging enabled). | |
| * Reproduce the problem. | |
| * Select "Send Better BibTeX debug report..." from the help menu. | |
| Once you hit that submit button, you'll get a special red debug ID. Just share that with `@retorquere` in this issue thread. If the question is regarding an export, don't forget to include what you see exported and what you expected. | |
| By sharing your debug log, you're giving `@retorquere` a clearer picture of your setup and the items causing the issue. It's like a superhero cape for him – he can swoop in and tackle the problem much faster. | |
| We totally get that your time is valuable, and we appreciate your effort in helping `@retorquere` help you. You might be surprised at how much this simple step speeds up the whole process. | |
| Thanks a bunch! | |
| **PS: If the Debug Log menu does not appear, or it does not send the debug log** | |
| A fallback option is available under "Help" > "Send debug log to file.io". | |
| message.no-close: Thanks for the feedback! Just so you know, GitHub doesn't let me control who can close issues, and @retorquere likes to leave bug reports and enhancements open as a nudge to merge them into the next release. |