Zentrik + GitHub

1. Open Settings → Integrations → GitHub.
2. Choose Connect GitHub.
3. GitHub opens the Zentrik GitHub App installation flow.
4. Choose the organization or account.
5. Select the repositories Zentrik should read.
6. Choose Install & Authorize.
7. GitHub redirects back to Zentrik.
8. Under Tracked repositories, choose the installed repositories whose delivery activity belongs in this workspace, then choose Apply.

Repositories selected in GitHub are installed repositories: the set the GitHub App can read. After you return, choose the tracked repositories that should feed this Zentrik workspace. You can track one repository, several repositories, or all installed repositories.

Open the searchable repository picker, select or clear repositories, and choose Apply. Zentrik verifies the complete set before saving it, so a repository that is no longer available cannot leave the workspace with a half-updated selection. At least one repository must remain tracked. If the installation contains only one repository, Zentrik selects it automatically.

Add a trailer line to the pull request description. Most delivery work should link directly to its initiative:

Zentrik: INITIATIVE-7

Link to a specific idea when the pull request implements or validates that idea directly:

Zentrik: closes IDEA-42

You can reference several records when each relationship is useful. Do not add both an initiative and its idea only to increase coverage: initiative views already roll up pull requests linked through promoted ideas.

Every initiative and idea shows its exact related-work reference, so a person or agent can copy it into the pull request. Initiative reads through Zentrik's agent tools also return the exact related and completion trailers.

The verb after Zentrik: sets what the link means.

Closing verbs are close, fix, resolve, complete, and deliver (and their tenses, such as fixes or resolved). Anything else, or no verb at all, relates.

For an initiative, shipped closing work produces a completion suggestion for a person to confirm. For an idea, a direct closing trailer can move it to its configured shipped status after Zentrik has same-repository production evidence. Related work does neither.

A branch whose name contains a record id, such as jab/initiative-7-timeline or jab/idea-42-timeline, also links the pull request.

Branch references always relate. A branch is a place to work, not a completion claim. Use a Zentrik: closes trailer when the pull request completes the record.

You do not have to use a reference. You can link or unlink a pull request directly from the Delivery tab on an initiative, or the Development panel on an idea.

A manual link starts as related work. Add a Zentrik: closes … trailer to the pull request if it completes the record. Zentrik applies that explicit intent to the existing link.

• On an initiative, the Delivery tab lists its linked pull requests and their state. The tab unlocks once GitHub is connected.
• On an idea, the Development panel shows the same for that idea.
• On Home, work with open pull requests appears as in delivery.

When several repositories are tracked, these surfaces combine their activity. Pull request and branch rows keep the repository name visible so repeated branch names and pull request numbers stay clear.

Zentrik advances status from facts and leaves initiative completion to the team. The first open pull request linked directly to an initiative, or through one of its promoted ideas, moves the initiative to In progress. Zentrik suggests completion only from shipped closing work; a person decides whether the initiative is complete.

A merge is not the same as reaching customers. If a repository promotes work through a delivery branch (for example develop) into a production branch (for example main), Zentrik reads that pattern from its release history and separates the two states:

• Merged work is pre-production until a release promotes it.
• Only work that reached the production branch reads as shipped.

When Zentrik can observe a production boundary, closing work suggests completion only after it reaches production. If Zentrik cannot establish that boundary, merged closing work can still produce a completion suggestion labeled production unverified. The team must confirm the product outcome.

Zentrik resolves this model separately for every tracked repository. A release in one repository never marks similarly named branches in another repository as shipped.

For automatic Idea shipping, an owner or admin must choose the production branch under Idea shipping in the GitHub integration. Choose the delivery branch too if work first merges elsewhere. These can be the same branch. Saving checks existing closing pull requests; leaving production unset keeps automatic shipping off. Branch patterns observed from history do not turn it on.

In an Idea's Development panel, choose Completes this idea to copy its closing reference. One qualifying closing pull request is sufficient. The Idea record shows when it shipped and the recorded pull request evidence, including after GitHub is disconnected. You can also change status manually. Reopening preserves the receipt and prevents earlier evidence from shipping the Idea again.

Shipment records arrival on the configured branch. It does not verify deployment success or customer availability. If settings save but Idea updates fail, use Refresh GitHub to retry.