Name Date Size #Lines LOC

..--

README.mdH A D25-Apr-2025261 54

binary_ios_build.shH A D25-Apr-20251.5 KiB4835

binary_ios_test.shH A D25-Apr-2025520 2014

binary_ios_upload.shH A D25-Apr-20253 KiB7657

binary_linux_build.shH A D25-Apr-20251.1 KiB3522

binary_linux_test.shH A D25-Apr-20254.8 KiB136117

binary_macos_build.shH A D25-Apr-2025405 1611

binary_macos_test.shH A D25-Apr-2025900 3524

binary_populate_env.shH A D25-Apr-20256.8 KiB192145

binary_upload.shH A D25-Apr-20253 KiB12697

binary_windows_build.shH A D25-Apr-2025749 3123

binary_windows_test.shH A D25-Apr-2025267 1810

driver_update.batH A D25-Apr-2025492 96

functorch_doc_push_script.shH A D25-Apr-20251.3 KiB4829

publish_android_snapshot.shH A D25-Apr-20251.7 KiB4734

trigger_azure_pipeline.pyH A D25-Apr-20254.4 KiB158121

README.md

1All the scripts in this directory are callable from `~/workspace/.circleci/scripts/foo.sh`.
2Don't try to call them as `.circleci/scripts/foo.sh`, that won't
3(necessarily) work.  See Note [Workspace for CircleCI scripts] in
4job-specs-setup.yml for more details.
5