What Deixic does with GitHub.

How Deixic helps with GitHub.

Read information

Review actions, branches and checks from GitHub as evidence and to check state.

Choose the actions

Deixic supports actions on checks, contents and issues. Grant only the tools and permissions the task needs.

Keep your decisions

Deixic checks your policy before a change; sensitive changes wait for a named approver. The action record keeps the decision and result.

10 of 12 changing operations require approval. See how approvals work.

Example workflow

Show that changes to the default branch were reviewed

For this repository, read the recent pull requests merged into the default branch and their review and check results. List any merged change that had no approving review, and prepare a CODEOWNERS file if the repository has none.

1. Resolve the repository and its default branch. Read the merged pull requests, their reviews, and the check results on each head commit. A change with no approving review is a CC8.1 exception; record the pull request number and repository together.
2. Read the repository tree and file contents for a CODEOWNERS file. If it is missing, prepare one that names the owning team for each path.
3. Writing a file is an approval step. The named approver sees the repository, path, and exact content, and records a reason before Deixic commits it.
4. After the commit, read the file back at the new revision and compare it to the approved content. Post a check on the commit that records the result, and keep the check and commit identifiers as the receipt.
5. For missing review requirements, prepare a branch-protection change or an increase to the required-review count for approval, then read the rule back. For a confirmed departure, prepare organization membership removal for approval and check the member list after the change.

Check before you continue: CODEOWNERS only blocks merges when the branch protection rule requires code owner review. Reading the file back proves the file is there, not that the rule is enforced. Confirm the rule in the repository settings.

Provider reference: About code ownersBranch protection REST APICheck runs REST API

Use your existing agent with Deixic. Calls you route through Deixic follow your access and approval policy.

Provider access

Supported GitHub reads and actions.

Choose the reads and actions your task needs. Your connection’s permissions and your agent’s access determine what it can use.

Permissions

Choose the access for GitHub.

Select the installation and repositories the task needs; an installation on one account does not grant access to repositories in another.

Find GitHub in the appManage connected accounts

To work with Dex in GitHub, see Dex on GitHub.

Connection

GitHub App

Supported operations

Read and act

Reads

11

Actions

6

Provider permissions

Grant only the permissions needed for the task.

What you need to connect

• App ID
• Installation ID
• Private key
• Webhook secret (optional)

Deixic checks calls routed through its gateway and requests approval when your policy requires it.

Reference and troubleshooting

GitHub operation reference, troubleshooting, and questionsSOC 2 for GitHub

Guides for work in GitHub

Read the connected-systems series

Connectors for related work