GitHub Integration

Connect Deslicer AI agents to your GitHub repositories. Agents can search repos, read files, create branches, push configs, and open pull requests — all via the GitHub MCP.

Navigation

• Parent: Integrations
• Related: Slack | Data Onboarding

---

Capabilities

With GitHub enabled, agents can:

• Search repositories — find repos by name or topic across your authorized organizations
• Read files — browse repository structure and read file contents
• Create branches — create feature branches from any base branch
• Push files — upload or update files in a repository
• Create pull requests — open PRs with titles, descriptions, and target branches

The GDI Onboarding Agent uses GitHub to push generated Splunk config packages and open pull requests for code review. Other agents use it for code context and PR analysis.

Use Cases

• Data onboarding — GDI agent pushes generated Splunk apps to a repo and opens a PR for team review
• Code context — agent reads your Splunk app or config repo when helping with SPL or props
• PR review — agent summarizes PR changes or suggests improvements
• Config management — agent pushes updated configs to version control automatically

Setup

1. Go to Settings → Integrations → GitHub.
2. Enter a GitHub personal access token (PAT) with repo scope.
3. Select the repos and pull_requests toolsets to enable.
4. Save.

Agents can now interact with your GitHub repos when relevant to the task. The GDI Onboarding Agent uses search_repositories, create_branch, push_files, and create_pull_request tools during the data onboarding workflow.

Publish Path Rules

Each GitHub integration can restrict where agents create or update files. Open the integration in Settings → Integrations → GitHub (or edit an existing configuration from the tool sheet) and scroll to Publish path rules.

The card header shows Allowing all paths when both lists are empty, or a count such as 3 allowed · 2 blocked when rules are active.

Pattern syntax

• * matches one path segment (for example, apps/* matches apps/TA-acme but not apps/TA-acme/default)
• ** matches any depth (for example, docs/** matches docs/guide/setup.md)
• Press Enter to add each pattern to the list

Suggested patterns

Common allow-list starters include docs/**, apps/**, cca/**, .github/workflows/**, and README.md. Common block-list entries include .github/**, **/secrets/**, and **/*.pem.

Publish path rules apply to every agent that uses the integration — the GDI Onboarding Agent and any custom agent with GitHub enabled share the same policy for that configuration.

Permissions

You control which repos the integration can access via your personal access token's scope. Use fine-grained tokens to limit access to specific repositories or organizations.