Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Record warnings from the Xcode rules as structured information in dummy actions so that we can test them #333

Draft
wants to merge 3 commits into
base: bj/fork-the-xcode-rules-from-bazel-built-in-starlark-into-apple_support
Choose a base branch
from

Conversation

brentleyjones
Copy link
Collaborator

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

…k (except those that can't be migrated because they use experimental flags).

PiperOrigin-RevId: 630133992
(cherry picked from commit d5a60a6)
PiperOrigin-RevId: 631018102
(cherry picked from commit f1bbadc)
…my actions so that we can test them

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
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