Pro and Team guide · CI/CD

A job moves from Development to Production by a pull request in its GitHub repository. Merging it runs a GitHub Action that promotes the job: reviewed, recorded, and the same every time.

Connect GitHub

1. Press Connect GitHub and install the Ductile AI GitHub app on your GitHub organisation or account, choosing the repositories it may use.
2. Choose the Repository, and a Folder (optional) if it holds other code too, then press Connect repository.

The repository gets a branch for each environment - main is Development, prod is Production, uat is Test (used on Enterprise) - and the workflow that promotes, .github/workflows/promote.yml, which runs when a pull request is merged into uat or prod.

How a job moves

1. Build in Development. Change the job in the console; Commit Development writes its processes to the Development branch - each process a .bp file, and credentials.json naming the credentials it needs.
2. Open the pull request. Promote to Production (pull request) opens one from Development to Production. Your team reviews the change in GitHub like any code: required reviewers and branch protection apply.
3. Merge. Merging into the Production branch runs the promote workflow.
4. The Action proves who it is. It presents a GitHub OIDC token - nothing is stored in GitHub, no key, no secret - and the console checks that it comes from your repository and names the Production branch.
5. The console promotes. It reads the job at exactly the merged commit and sets Production's processes from it. Each credential named in credentials.json is bound to Production's own credential of that name; secrets never travel through Git.
6. On record. The run of the Action, the commit and the promotion are recorded; Production's runs start from the new version.

A job of its own. Promotion is per job: a job promotes from its own repository. A job kept in a shared folder with others is given its own repository first, so one merge never carries another job.

Last updated October 29, 2026