Lines Matching +full:- +full:- +full:github +full:- +full:issue

1 # Contributing to SPIR-V Tools
5 We organize known future work in GitHub projects. See
6 [Tracking SPIRV-Tools work with GitHub projects](https://github.com/KhronosGroup/SPIRV-Tools/blob/m…
9 To report a new bug or request a new feature, please file a GitHub issue. Please
11 [issues](https://github.com/KhronosGroup/SPIRV-Tools/issues) and
12 [projects](https://github.com/KhronosGroup/SPIRV-Tools/projects). If the bug has
14 [here](https://github.com/KhronosGroup/SPIRV-Tools/issues/new).
16 When opening a new issue for a bug, make sure you provide the following:
20         issue is about. Simply using "Segfault in spirv-opt" is not helpful
27         to possibly realize the bug is related to another issue.
30 [issues](https://github.com/KhronosGroup/SPIRV-Tools/issues) as well. Please
31 create a new issue, as with bugs. In the issue provide
39 [Khronos Open Source Contributor License Agreement](https://cla-assistant.io/KhronosGroup/SPIRV-Too…
43 need to be sure of various other things -- for instance that you'll tell us if
49 [README.md](https://github.com/KhronosGroup/SPIRV-Tools/blob/main/README.md)
54     [Google C++ Style Guide](https://google.github.io/styleguide/cppguide.html).
55     Running `clang-format -style=file -i [modified-files]` can help.
58     solution, and references the issue if applicable.
60     `Fixes https://github.com/KhronosGroup/SPIRV-Tools/issues/1234` When you do
61     this, the issue will be closed automatically when the commit goes into
81 The formal code reviews are done on GitHub. Reviewers are to look for all of the
85     [Google C++ Style Guide](https://google.github.io/styleguide/cppguide.html)
97     scenarios? The respective SPIR-V dialects are slightly different.
100 *   For SPIR-V transforms: The module is changed, but the analyses are not
101     updated. For example, a new instruction is added, but the def-use manager is
102     not updated. Later on, it is possible that the def-use manager will be used,
110 We intend to maintain a linear history on the GitHub main branch, and the
112 always-working history is easier to understand and to bisect in case we want to
114 ….github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-re…
115 button on the GitHub web interface. All other ways of merging on the web
121     [failing smoke test](#failing-smoke-test).
125 The squash-and-merge button will turn green when these requirements are met.
132 [shaderc](https://github.com/google/shaderc) fails to build with the change. If
135 the time [Glslang](https://github.com/KhronosGroup/glslang) needs to be updated
136 to account for the change in SPIR-V Tools.
145 If the Github actions tests do not run on a PR, they can be initiated by closing