Lines Matching refs:good

4 …nt in the Vulkan header integration process, include the fix in the known-good update commit, prop…
12 Update the Vulkan-Loader, Vulkan-ValidationLayers, and Vulkan-Tools known-good files
16 …good of a repository needs to be updated, all repositories of interest that appear in its known-go…
23 * Typically the Vulkan-Loader's known-good is updated first, but the Vulkan-ValidationLayers known-…
24 …good files (see the [update LunarG known-good section](https://github.com/KhronosGroup/Vulkan-Head…
47 … warnings must be resolved and included in the pull request for the repository's known-good update.
61 ### 5. Update the known-good files
63 …good commits for each dependent repository. Some repositories require an additional known-good fil…
73 …good files, etc.) in a single commit on a branch and push it up to the online repository. In Vulka…
77 Verify the branch with the proposed known-good commit is rebased on the tip of `master` and create …
81 Once the known-good update PR is approved, the assignee will rebase the approved commits onto the `…
83 ### 9. Tag the known-good commit
85 Once approved and rebased onto `master`, the known-good update commit must be marked with a version…
87 ## Update the LunarG/VulkanTools and LunarG/VulkanSamples known-good files
89 Updating the Known-good files in LunarG repositories follows the same steps as updating the known-g…
96 ### Updating LunarG known-good files