Consider moving unreleased changes to a separate "Unreleased.md" file #133
This file contains hidden or 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: Needs Repro | |
| on: | |
| issues: | |
| types: [labeled] | |
| permissions: | |
| issues: write | |
| jobs: | |
| comment: | |
| name: Post repro instructions | |
| runs-on: ubuntu-latest | |
| if: github.event.label.name == 'Needs Reproduction' | |
| steps: | |
| - name: Post repro comment | |
| uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 | |
| with: | |
| script: | | |
| await github.rest.issues.createComment({ | |
| owner: context.repo.owner, | |
| repo: context.repo.repo, | |
| issue_number: context.issue.number, | |
| body: `👋 Thanks for the report! We've added the \`Needs Reproduction\` label because we need a minimal reproduction to investigate further. | |
| Please provide a link to a **public GitHub repository** that reproduces the issue with as little code as possible. Our [repro guide](https://github.com/getsentry/sentry-dotnet/blob/main/.github/repro.md) has tips on how to create one. | |
| Some quick hints: | |
| - Start from a fresh \`dotnet new console\` (or similar) project | |
| - Add only the Sentry NuGet package(s) relevant to the bug | |
| - Include the exact SDK version number and your \`SentrySdk.Init\` / \`UseSentry\` call (with the DSN blanked out) | |
| Alternatively, if the issue only manifests in your own codebase, you could try gradually removing code until you have a minimal repro.` | |
| }); |