-
Notifications
You must be signed in to change notification settings - Fork 536
.gitignores for ios demo artifacts #8153
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
base: main
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/8153
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit b5a92cb with merge base 78752a0 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@pytorchbot label "topic: not user facing" |
be694d5
to
5a90013
Compare
Looks good to me. Can you rebase please? |
98de889
to
519ac94
Compare
I'm having to manually rebase each time new commits come up on the main branch. You have my permission to rebase it yourself whenever you do the final review. |
519ac94
to
b5a92cb
Compare
Summary
Following the iOS Demo app instructions generates files that are not tracked in version control. This updates the main
.gitignore
, and adds a new.gitignore
specific to the generated iOS Xcode project.Test plan
This has been tested, in the sense that I have run through the instructions to the end of the iOS demo without issue, and only needed to make the
.gitignore
changes so I didn't have the build artifacts appear as untracked in version control.It is possible these changes may lead to undesired effects in esoteric unofficial workflows with this repo, but I can't know that unless someone speaks up about it. I couldn't find any prior discussion about this.