Xavier Bonaventura

I started preparing also to convert the uic call to a rule. But in this case I saw that there is no test in the CI. https://github.com/limdor/bazel_rules_qt/commit/6f193b4dae073d44427d972fdad81ced9432b4f5 If you have...

@justbuchanan In case you are interested, I started working on a way to autodetect the system https://github.com/limdor/bazel_rules_qt/pull/6, next step will be to read it from an environment variable https://github.com/limdor/bazel_rules_qt/issues/13

@sgowroji the style guide still discourages to use = 1 and there are still several places where the warning still suggests to use =1. https://github.com/bazelbuild/bazel/blob/master/src/main/java/com/google/devtools/build/lib/rules/cpp/CcLibrary.java#L511 Could you just reopened this...

You can use x for the wildcard, for example 4.x

I would also be interested on knowing how people is supposed to use strict and migrate. I just naively run `bazelisk --strict build //...` and I also saw this error...

I would like if before closing it someone from Bazel team could comment on it. What is the official way for the user to migrate to a new bazel version?...

If I remove the quotes it works and does not display the warning anymore. I also tried what happens if I put the buildifier.exe into a folder with spaces, then...

It would be nice if this would go it, I guess it got forgotten https://github.com/bazelbuild/bazel/pull/15960

@sgowroji it is not straightforward and hard to flip and fix everything at once. I created a pr that all checks are passing that move some of the changes there....

I created another PR that prepare some other parts https://github.com/bazelbuild/bazel/pull/15339