Conversation
|
Can we also request the spirv? I think that would be most usefull. |
arirawr
left a comment
There was a problem hiding this comment.
Couple small things but LGTM
|
@VZout Sure, what's the command for getting the version? |
Co-authored-by: Ari V <ari.vaniderstine@embark-studios.com>
Co-authored-by: Ari V <ari.vaniderstine@embark-studios.com>
|
But a version from the releases would also be enough if they didn't clone. |
|
@VZout Sorry, I meant for getting the version from the spirv tools? |
|
Do you mean the version of the spec that the output spir-v is using? That should be embedded in the binary i think. |
|
spirv-tools version: run |
I mean what you were asking about above. |
|
Yeah I mean request the SPIR-V binary as a attachment. So we can look through the SPIR-V our project generated when debugging their issue. |
|
Ah I see now. I've added a mention of it. Let me know if you think it should be more. Since its binary they'll have to include a link to somewhere else as GitHub issues doesn't allow arbitrary attachments. |
* Add bug report template * Update .github/ISSUE_TEMPLATE/bug_report.md Co-authored-by: Ari V <ari.vaniderstine@embark-studios.com> * Update .github/ISSUE_TEMPLATE/bug_report.md Co-authored-by: Ari V <ari.vaniderstine@embark-studios.com> * Update bug_report.md * Update bug_report.md Co-authored-by: Ari V <ari.vaniderstine@embark-studios.com>
resolves #57