Robert Lin 1ff9bc70eb sg-binary-release: stamp with GitHub release name (#62176) ... We have nice release names in https://github.com/sourcegraph/sg/releases, but it's not actually programmatically available - this causes a discrepancy between the `sg` version one might pull, and the version of `sg` that is known in-code, and means that we can't do something like #62134. This change adds a `ReleaseName` variable to be stamped at build/release time, and updates a few references to `BuildCommit` where I think it might be more prudent to report `ReleaseName` instead, and also fixes some yellow squiggles in my IDE on files I visited (sorry) and some noisy `-v` output (sorry again) ## Test plan ``` $ go build -ldflags "-s -w -X main.BuildCommit=$(git rev-list -1 HEAD .) -X main.ReleaseName=hello-world" -o ./sg ./dev/sg $ ./sg version hello-world $ ./sg -v version Version: hello-world Build commit: b23db0be5e ```		2024-04-25 08:10:55 -07:00
..
ISSUE_TEMPLATE	chore(sg): remove issue template for sg (#62083)	2024-04-22 13:25:47 +00:00
PULL_REQUEST_TEMPLATE	Update .github/PULL_REQUEST_TEMPLATE/browser-extension.md order (#33407)	2022-04-05 17:39:55 +06:00
workflows	sg-binary-release: stamp with GitHub release name (#62176)	2024-04-25 08:10:55 -07:00
PULL_REQUEST_TEMPLATE.md	docs: elaborate on the purpose of test plans (#55732)	2023-08-10 12:45:02 +00:00
teams.yml	Update teams.yml for product platform teams (#61242)	2024-03-18 14:45:24 -04:00
test.CODEOWNERS	Stop tagging @mrnugget (#59184)	2023-12-21 22:04:15 +00:00