Palantir Foundry CI and Review Gates

Overview

Build the quality gate around Foundry Code Repository branches, automatic checks, unit tests, and pull-request review. External Git hosting may mirror evidence, but it must not replace the checks that Foundry runs against repository inputs, outputs, dependencies, and platform builds.

Prerequisites

• Identify the Foundry enrollment, Code Repository, target branch, owned datasets, and release owner.
• Confirm whether the repository uses Python transforms, TypeScript, or another supported project type.
• Read references/official-docs.md and inspect the repository's effective CI and branch settings before proposing changes.
• Use a sandbox branch and non-production data until the checks and rollback path are proven.

Current Contract

• A commit to a Code Repository branch runs automatic checks; the Checks tab is the primary result surface.
• Python unit tests can participate in repository CI when configured according to the repository's supported build layout.
• Transform input and output declarations are evaluated by CI and cannot be chosen dynamically at build time.
• A pull request can require approving review before merge, and reviewers can inspect dataset impact for transform changes.