test buckify

.github/workflows/build-and-test.yml

@@ -13,5 +13,12 @@ jobs:
     steps:
       - uses: actions/checkout@v4
       - uses: Swatinem/rust-cache@v2
+      - run: echo CARGO_HOME=$GITHUB_WORKSPACE/.cargo >> $GITHUB_ENV
+        shell: bash
       - run: cargo build --locked
       - run: cargo test
+      - run: |-
+          cd example
+          ./setup.sh # run reindeer buckify
+          cat ./third-party/BUCK
+        shell: bash

example/setup.sh

@@ -4,19 +4,19 @@
 # This source code is licensed under the MIT license found in the
 # LICENSE file in the root directory of this source tree.
 
-# Set up vendored directory
+# Generate file 'example/third-party/BUCK'.
 
 set -e
 
 (cd ..; cargo build)
 
-# Vendor the crates into third-party/vendor
-# This will resolve all the dependencies, and create or update third-party/Cargo.lock as required.
-# Typically you would then checkin Cargo.lock and all the vendored code in third-party/vendor
-../target/debug/reindeer --third-party-dir third-party vendor
-
 # Build a BUCK file to build third-party crates.
-# This is separate from vendoring as you may need to run it a few times if it reports needing a fixup.
-# It will create a template fixup.toml which you can edit as needed. You would typically commit
-# these fixups and the generated third-party/BUCK in the same commit as above.
+#
+# This will resolve all the dependencies, and create or update
+# third-party/Cargo.lock as required.
+#
+# It will create a template fixup.toml which you can edit as needed. You would
+# typically commit these fixups and the generated third-party/BUCK in the same
+# commit as above.
+
 ../target/debug/reindeer --third-party-dir third-party buckify