Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2025-08-07T04:26:30+00:00 2025-08-07T04:26:30+00:00 Jay Kwak 82421531+jkwak-work@users.noreply.github.com 2025-08-07T04:26:30+00:00 urn:sha1:1088e57b63ae49be885d312dfad6e02057f29083 This commit adds a new command-line argument for `docs/script/release-note.sh`, which is `--previous-release-hash`. It will allow us to generate the release note at more finer granularity. The current help message is following, ``` Usage: ./docs/scripts/release-note.sh [--since DATE | --previous-release-hash HASH] --since DATE Generate notes since the given date (e.g., 2025-08-06) --previous-release-hash HASH Generate notes since the given commit hash Legacy usage (deprecated): ./docs/scripts/release-note.sh DATE ``` Fixes - https://github.com/shader-slang/slang/issues/5188 - https://github.com/shader-slang/slang/issues/6887 --------- Co-authored-by: slangbot <ellieh+slangbot@nvidia.com> Co-authored-by: slangbot <186143334+slangbot@users.noreply.github.com> Co-authored-by: Ellie Hermaszewska <ellieh@nvidia.com> 2025-07-23T19:09:45+00:00 Jay Kwak 82421531+jkwak-work@users.noreply.github.com 2025-07-23T19:09:45+00:00 urn:sha1:559c8307d7537319c9f2b3f3d386d8b9b147aba3 The release note script was trying to retrieve additional label information from the "issue" but when parsing logic is not reliable. When the issue has a link to a repo other than Slang, it printed error message. An example is #7826 that has a link to an external repo, https://github.com/llvm/llvm-project/issues/79043 2024-10-30T05:45:53+00:00 Ellie Hermaszewska ellieh@nvidia.com 2024-10-30T05:45:53+00:00 urn:sha1:22d1e345037eea853e54b84af718340cb9776513 * format yaml and json * format shell scripts 2024-09-25T14:01:11+00:00 Ellie Hermaszewska ellieh@nvidia.com 2024-09-25T14:01:11+00:00 urn:sha1:88623edb8120333d48a9ebdec73063f94a10282e Co-authored-by: Jay Kwak <82421531+jkwak-work@users.noreply.github.com> 2024-09-17T05:24:44+00:00 cheneym2 acheney@nvidia.com 2024-09-17T05:24:44+00:00 urn:sha1:25d155937402120292cff9e6f5a31c1d45a2ecbf Add a gh.exe search path that works with cygwin installations. Do not bail out from the breaking changes loop when a change is found without PR#. Instead, continue to the next one. This fixes an issue where [BREAKING] changes appear in the detailed change list by not in the summary of breaking changes. 2024-08-28T01:13:52+00:00 Jay Kwak 82421531+jkwak-work@users.noreply.github.com 2024-08-28T01:13:52+00:00 urn:sha1:5645ecfc9d487a5fe612f17d970332a93ed40c47 * Script for generating a release note Related to #4718 * Adding a comment about how to run --------- Co-authored-by: Yong He <yonghe@outlook.com>