Matt Robinson

I'm having good luck with the following in my root `BUILD.bazel`: ```Starlark load("@com_github_bazelbuild_buildtools//buildifier:def.bzl", "buildifier") buildifier( name = "buildifier-fix", lint_mode = "fix", mode = "fix", ) ``` Then ran via: ```...

Is there any particular reason for not using `--swift_opt=FileNaming=PathToUnderscores` in this case as it's (probably) more portable than `--swift_opt=FileNaming=FullPath` when used in the downstream `swift_proto_library` case? https://github.com/bazelbuild/rules_swift/blob/225180bf8ac2b2f4cbda77dd1ef07a407aea4231/swift/internal/swift_protoc_gen_aspect.bzl#L174

In this case, just trying to think about portability of the source for the downstream underlying `swift_proto_library`. Since `--swift_opt=FileNaming=FullPath` + `foo/bar/user.proto` & `foo_bar/user.proto` will fail when used in the underlying...

Closed. Thanks, @luispadron! Please open a new issue if there's missing functionality in the new `xcarchive` rule.

Hello there. Is it easy for you to create a simple repro example for us to debug?

> You need to downgrade your mac to macOS 11.2.3 or below. What's the reason for macOS 11.2.3 requirement? Changes in the underlying `mremap_encrypted` implementation?

See if this is fixed by https://github.com/bazelbuild/rules_apple/pull/1703, @mcfans.

I was working on this earlier this week. I am moving the bundle and XCTestRun creation into separate utility scripts that are used by the xctestrun_runner template. Hopefully I can...

Is this for running tests or using Xcode via project generation like `rules_xcodeproj`?

This is something that's been implemented by dozens of companies in slightly different ways for the same goal. Unifying the structure with a highly flexible DSL to describe this would...