Skip to content

Conversation

@brentleyjones
Copy link
Collaborator

PiperOrigin-RevId: 631862483
(cherry picked from commit 0f6c6a3)

brentleyjones referenced this pull request May 17, 2024
…my actions so that we can test them.

PiperOrigin-RevId: 631862483
@brentleyjones brentleyjones force-pushed the bj/fork-the-xcode-rules-from-bazel-built-in-starlark-into-apple_support branch from 4d43dbc to 0642071 Compare May 31, 2024 12:33
@luispadron luispadron force-pushed the bj/fork-the-xcode-rules-from-bazel-built-in-starlark-into-apple_support branch from 0642071 to 74f5f42 Compare January 22, 2025 20:00
@luispadron luispadron force-pushed the bj/fork-the-xcode-rules-from-bazel-built-in-starlark-into-apple_support branch 4 times, most recently from 2bd7b3d to f7d3a5c Compare March 29, 2025 05:30
Base automatically changed from bj/fork-the-xcode-rules-from-bazel-built-in-starlark-into-apple_support to master March 31, 2025 15:30
@keith
Copy link
Member

keith commented Jul 5, 2025

think this is mergable if conflicts were fixed?

…my actions so that we can test them

PiperOrigin-RevId: 631862483
(cherry picked from commit 0f6c6a3)
@brentleyjones brentleyjones force-pushed the bj/record-warnings-from-the-xcode-rules-as-structured-information-in-dummy-actions-so-that-we-can-test-them branch from dc17129 to d6b4176 Compare December 1, 2025 20:10
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.

4 participants