meta: add repro guide and needs-repro automation#4975
Conversation
- Add .github/repro.md with guidance on how to create a minimal reproduction for bug reports - Update .github/ISSUE_TEMPLATE/bug_report.yml to reference the repro guide at the top of the form and in the 'Steps to Reproduce' field - Add .github/workflows/needs-repro.yml GitHub Actions workflow that automatically posts a comment with repro instructions and a link to the guide whenever the s/needs-repro label is added to an issue Closes #4105 Co-Authored-By: GitHub Copilot <copilot@github.com>
Semver Impact of This PR⚪ None (no version bump detected) 📋 Changelog PreviewThis is how your changes will appear in the changelog. This PR will not appear in the changelog. 🤖 This preview updates automatically when you update the PR. |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4975 +/- ##
==========================================
+ Coverage 73.86% 73.95% +0.08%
==========================================
Files 496 497 +1
Lines 17951 17966 +15
Branches 3516 3516
==========================================
+ Hits 13259 13286 +27
+ Misses 3833 3823 -10
+ Partials 859 857 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Flash0ver
left a comment
There was a problem hiding this comment.
I believe feat is not quite the right commit label.
I think meta would fit better.
See also https://develop.sentry.dev/engineering-practices/commit-messages/
Co-authored-by: Stefan Pölz <38893694+Flash0ver@users.noreply.github.com>
Done. I also simplified the instructions. There was a lot of contnet in there anticipating problems / anger with us asking for a repro. They maybe get that at Microsoft but we've never really had a problem with this tbh, so I think we should leave it out initially. If we start to get push back when asking for minimal repros, we can add it back in later. |
Summary
Resolves #4105
Changes
.github/repro.md– New guide explaining what a minimal reproduction is, why we ask for one, how to create it, and what to avoid. Adapted from the .NET MAUI repro guide but tailored for the Sentry .NET SDK..github/ISSUE_TEMPLATE/bug_report.yml– Added a markdown block at the top of the bug report form linking to the new guide, and updated the "Steps to Reproduce" field description to reference the guide..github/workflows/needs-repro.yml– New GitHub Actions workflow that automatically posts a comment with repro instructions and a link to the guide whenever theNeeds Reproductionlabel is added to an issue.#skip-changelog