Skip to content

chore(tools): stop tracking the changelog-site build output #2192

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sbaum1994 merged 2 commits into from
Oct 1, 2026
Merged

chore(tools): stop tracking the changelog-site build output #2192

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9753f15
chore(tools): stop tracking the changelog-site build output
RawJat Sep 30, 2026
bd4e9e3
Merge branch 'main' into rawjat/fix/untrack-changelog-site-binary
RawJat Oct 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions tools/changelog-site/.gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
# Build output from `go build` in this directory.
/changelog-site
Binary file removed tools/changelog-site/changelog-site
View file
Open in desktop
Binary file not shown.
3 changes: 1 addition & 2 deletions tools/ci/check-go-tools
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,8 +79,7 @@ for m in "${modules[@]}"; do
#
# With a main package, plain `go build ./...` writes the executable into the
# working directory, which under -C is the module itself. That leaves binaries
# behind and, for tools/changelog-site, rewrites one that is committed, so the
# output goes to a scratch directory.
# behind in the source tree, so the output goes to a scratch directory.
#
# With no main package, `go build -o <dir> ./...` is itself an error: "no main
# packages to build". A library-only module under tools/ is perfectly valid,
Expand Down
Loading