-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add a reproducer header #124
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #124 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 2 2
=========================================
Hits 2 2 ☔ View full report in Codecov by Sentry. |
CI here doesn't actually seem to run this action in its entirety... that should be fixed. |
96d4d60
to
960deee
Compare
Co-Authored-By: Sukera <[email protected]>
960deee
to
1f9c517
Compare
Unfortunately I don't think the git commit is very useful: for workflows triggered by pull requests, that'd be the merge commit, which isn't part of the base repo (for PRs opened from forks), that's only part of the target repo and you need to manually fetch the pr refs. For example you can see that the commit you show in the example above doesn't exist: IanButterworth/SimpleLooper.jl@87649fc |
Can be seen here: https://github.com/IanButterworth/SimpleLooper.jl/actions/runs/11406030258/job/31741980077?pr=5#step:6:43
cc. @Seelengrab