fix: work around SPM executable binary target bug

[jflan-dd]

Ignore errors from swift package commands caused by executable products depending on binary targets

Work around #1781 (comment)

[cgrindel]

@Mergifyio queue

[mergify]

queue

🟠 Waiting for conditions to match

• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
    • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
    • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-success = all_ci_tests
      • check-neutral = all_ci_tests
      • check-skipped = all_ci_tests
    • any of: [🛡 GitHub branch protection]
      • check-success = conventional_commit_check
      • check-neutral = conventional_commit_check
      • check-skipped = conventional_commit_check
• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

[cgrindel]

It looks like tidy is failing. I saw at least one issue with the doc string for the new function. Once things are green, we should be good to go.

[jflan-dd]

@cgrindel I updated the doc comment. bazel run //:tidy didn't catch it and I didn't realize that bazel test //... would test only the internal rule tests rather than also running the various example tests. I'll add that to my workflow when contributing here.

Addressed feedback.

[brentleyjones]

@Mergifyio queue

[mergify]

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at f834803

[cgrindel]

@cgrindel I updated the doc comment. bazel run //:tidy didn't catch it and I didn't realize that bazel test //... would test only the internal rule tests rather than also running the various example tests. I'll add that to my workflow when contributing here.

If you want to run the examples locally, there are //:smoke_integration_tests and //:all_integration_tests. However, I tend to create a draft PR and let GitHub run them in parallel.