Spawn previously stored cfg.Org on the buildkite_builds row, leaving empty when the workflow YAML didn't set tack.buildkite.org and relying on the read path to fall back to the provider's defaultOrg. That coupling let historical lookups drift: if defaultOrg ever changed, log fetches and webhook joins for older builds would silently target the wrong organisation.
Something went wrong. Try again.
Stitch any CI into Tangled
Something went wrong. Try again.
buildkite: persist resolved org on build mapping #44
This pull request has no versions submitted yet.