Skip to content
BoundaryKit

GitHub Actions

GitHub Actions — bind the evaluation result to the pull request head commit.

Where GitHub Actions enforces the boundary

Section titled “Where GitHub Actions enforces the boundary”

Bind the evaluation result to the pull request head commit. The adapter owns the provider credential. Propagate the decision ID into the provider trace so a retry can be matched to its original authorization.

  1. Read the BoundaryKit workspace using the adapter identity.
  2. Cache the revision only for this session.
  3. Forward the provider call after evaluation.
Terminal window
curl --fail-with-body "https://api.boundarykit.com/v2/integrations" -H "X-API-Key: $BKIT_KEY" -H "X-Organization-Id: $BKIT_ORG"

Inspect the receipt for GitHub Actions. Compare its organization and revision with the values in the fixture before interpreting the result. Match the provider request ID to the attempt number. Retries may produce multiple provider IDs for one decision.