Skip to content

Print Bazelisk version when startup flags are set.#646

Merged
meteorcloudy merged 1 commit intobazelbuild:masterfrom
fweikert:master
Dec 10, 2024
Merged

Print Bazelisk version when startup flags are set.#646
meteorcloudy merged 1 commit intobazelbuild:masterfrom
fweikert:master

Conversation

@fweikert
Copy link
Member

@fweikert fweikert commented Dec 9, 2024

When invoking Bazelisk with the version command, the output should always start with the Bazelisk version followed by the output of bazel version. However, previously this was not the case when startup flags were set, e.g. when calling bazelisk --nosystem_rc version.

When invoking Bazelisk with the `version` command, the output should always start with the Bazelisk version followed by the output of `bazel version`.
However, previously this was not the case when startup flags were set,
e.g. when calling `bazelisk --nosystem_rc version`.
@fweikert fweikert requested a review from meteorcloudy December 9, 2024 19:13
@fweikert
Copy link
Member Author

fweikert commented Dec 9, 2024

I noticed this while looking at our CI (which calls bazel --nosystem_rc --nohome_rc version).

@meteorcloudy meteorcloudy merged commit 8eec345 into bazelbuild:master Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants