Why it matters
When a contract changes, someone will later ask who changed it, why, and whether it was checked. If changes go straight to production, there is no answer. LakeLogic keeps every change as a draft until it is reviewed and merged, so each published version has a trail behind it.
What you can do
- Edit a contract without changing the live version.
- Bundle one or more drafts into a single pull request.
- See whether each change passes your standards before it merges.
- Compare a draft with the published version, and see every past version.
How to do it in LakeLogic
- Go to Govern → Contracts → Contract Studio and open the contract.
- Make your change and choose Save draft. The live contract does not change. The contract page shows the open change, for example "Draft 2, not in a pull request yet", and what it changes compared with the published version.
- Choose Create PR. It is disabled until the draft has no validation issues. To send several drafts together, use Create PR (N unpublished) on the Contract Studio list. Which Git providers: Create PR opens the pull request on GitHub or Azure DevOps. On GitLab and Bitbucket, LakeLogic pushes the branch but does not open the merge request or track the merge yet, so open it yourself. See Connect your tools.
- In the Create pull request window, review each change, pick the ones to include and submit. LakeLogic creates a branch, commits the contract files and opens the pull request.
- The pull request is checked against your standards. Follow the result in Govern → Contracts → Change Checks. See Stop bad changes before they reach production.
- Your team reviews and approves the pull request in your Git provider, as for any code change.
- Merge it. LakeLogic receives the merge from the repository, applies the change and marks the contract published. The standards are evaluated again at publish and the result is recorded.
The states a change moves through
| State | Meaning |
|---|---|
| Draft | Saved in LakeLogic. Not in a pull request yet, or in one that is still open. |
| In review | A pull request is open for it. |
| Approved | Ready to merge. |
| Published | Merged. This is now the live version. |
What you get
- The History tab on each contract lists its versions and compares a draft with the version it would replace.
- Change Checks keeps each change with its downstream impact and check results.
- Govern → Standards → Assessment History keeps every evaluation run and its decision.
- The pull request in your repository keeps the review, the approver and the merge commit.
Good to know
- Approval happens on the pull request in your Git provider. LakeLogic does not add a separate approval step on top of it.
- A change proposed by an AI assistant is approved by a person in LakeLogic, then published through a pull request like any other change. See Connect your AI assistant.
- You need a connected repository to open pull requests. See Connect your tools.