Skip to content

Handle .xcprivacy files in TargetSourcesBuilder.swift #7807

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

Merged
merged 4 commits into from
Jul 23, 2024

Conversation

MaxDesiatov
Copy link
Contributor

rdar://111119227

@MaxDesiatov
Copy link
Contributor Author

@swift-ci test

@MaxDesiatov MaxDesiatov changed the title Ignore .xcprivacy files in TargetSourcesBuilder.swift Handle .xcprivacy files in TargetSourcesBuilder.swift Jul 22, 2024
@MaxDesiatov
Copy link
Contributor Author

@swift-ci test

@MaxDesiatov MaxDesiatov enabled auto-merge (squash) July 22, 2024 21:18
@MaxDesiatov
Copy link
Contributor Author

@swift-ci test windows

@MaxDesiatov
Copy link
Contributor Author

@swift-ci test

@MaxDesiatov
Copy link
Contributor Author

@swift-ci test windows

@MaxDesiatov MaxDesiatov merged commit 6d154e7 into main Jul 23, 2024
5 checks passed
@MaxDesiatov MaxDesiatov deleted the maxd/ignore-xcprivacy branch July 23, 2024 23:22
MaxDesiatov added a commit that referenced this pull request Jul 24, 2024
MaxDesiatov added a commit that referenced this pull request Jul 24, 2024
Cherry-pick of #7807.

**Explanation**: There should be a file rule to automatically include or
ignore privacy manifests, given that we know the file name
**Scope**: isolated in code to a single file, only affects packages that
include privacy manifests.
**Risk**: low due to isolated scope.
**Testing**: added new test cases.
**Issue**: rdar://111119227
**Reviewer**: @bnbarham
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