Skip to content

Don't overwrite BUILD.bazel while making a release - #5376

Open
jwnimmer-tri wants to merge 1 commit into
nlohmann:developfrom
jwnimmer-tri:build-file-maintenance
Open

Don't overwrite BUILD.bazel while making a release#5376
jwnimmer-tri wants to merge 1 commit into
nlohmann:developfrom
jwnimmer-tri:build-file-maintenance

Conversation

@jwnimmer-tri

Copy link
Copy Markdown

Instead, add automation to 'develop' to ensure that it's always kept up to date.

Add missing header file 'logic.hpp'.

Re-apply e509007 "Remove alwayslink=True Bazel flag", which was accidentally reverted previously by the broken update script.

@jwnimmer-tri
jwnimmer-tri requested a review from nlohmann as a code owner August 11, 2026 16:17
@jwnimmer-tri

Copy link
Copy Markdown
Author

@Vertexwahn could you take a look?

Comment thread .github/workflows/check_bazel.yml Outdated
@Vertexwahn

Copy link
Copy Markdown
Contributor

@jwnimmer-tri LGTM - only the env variables MAIN_DIR and TOOL_DIR look unused to me...

Instead, add automation to 'develop' to ensure that it's always kept
up to date.

Add missing header file 'logic.hpp'.

Re-apply e509007 "Remove alwayslink=True Bazel flag", which was
accidentally reverted previously by the broken update script.

Signed-off-by: Jeremy Nimmer <jeremy.nimmer@tri.global>
@jwnimmer-tri
jwnimmer-tri force-pushed the build-file-maintenance branch from 560518e to e2b8828 Compare August 12, 2026 13:17
@jwnimmer-tri

Copy link
Copy Markdown
Author

Thanks! Fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants