next-intl/link is causing an error in tests
#23
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: Add comment | |
| on: | |
| issues: | |
| types: | |
| - labeled | |
| jobs: | |
| add-comment: | |
| if: github.event.label.name == 'reproduction-missing' | |
| runs-on: ubuntu-latest | |
| permissions: | |
| issues: write | |
| steps: | |
| - uses: peter-evans/create-or-update-comment@v3 | |
| with: | |
| issue-number: ${{ github.event.issue.number }} | |
| body: | | |
| Thank you for your report. | |
| Unfortunately, the reproduction is missing or incomplete, and as such we cannot investigate this issue. Please add a reproduction to the issue, otherwise it will be closed automatically. | |
| **Templates:** | |
| - [CodeSandbox (`app` directory)](https://codesandbox.io/p/sandbox/next-intl-bug-template-forked-yow8ep) | |
| - [CodeSandbox (`pages` directory)](https://codesandbox.io/p/sandbox/next-intl-bug-template-pages-krm37f) | |
| **Creating a good bug report takes time.** | |
| To help us resolve the issue quickly, please simplify the reproduction as much as possible by removing any unnecessary code, files, and dependencies that are not directly related to the problem. The easier it is for us to see the issue, the faster we can help you. | |
| Apart from the reproduction, make sure to include the precise steps on how to reproduce the issue, e.g.: | |
| 1. Open reproduction | |
| 2. Click on … | |
| 3. See error: … | |
| Thank you for your understanding! | |
| <details> | |
| <summary>FAQ</summary> | |
| **"I've included a reproduction, what is missing?"** | |
| This comment might have been added because your reproduction doesn't point to either a CodeSandbox or a public GitHub repository where the issue can be reproduced. | |
| Please make sure: | |
| 1. If you've linked to a CodeSandbox, make sure to save the latest changes. | |
| 2. If you've linked to a GitHub repository, make sure that you've committed and pushed the latest changes. | |
| 3. Linking to other resources, e.g. to the docs, unfortunately doesn't help to reproduce your issue. | |
| </details> |