# Glean Indexing API + GitHub integration > Sync your GitHub repositories, pull requests, issues, and code into Glean so everyone in your organization can find engineering knowledge without having to know where to look. **Canonical page:** https://tray.ai/connectors/glean-indexing-api-github-integrations/ **Glean Indexing API connector:** https://tray.ai/connectors/glean-indexing-api-integrations/ **Glean Indexing API documentation:** https://tray.ai/documentation/connectors/service/glean-indexing-api **GitHub connector:** https://tray.ai/connectors/github-integrations/ **GitHub documentation:** https://tray.ai/documentation/connectors/service/github ## Overview Engineering teams pour enormous amounts of knowledge into GitHub — code, documentation, pull request discussions, issue threads — and most of it stays invisible to anyone outside the immediate team. Connecting the Glean Indexing API with GitHub pulls that institutional knowledge into a unified enterprise search layer, where every stakeholder can actually find it. With tray.ai handling the connection, indexing runs continuously and automatically, so your Glean workspace stays current with what's actually in your repositories. GitHub is where engineering decisions get made, but the context behind those decisions — commit messages, README files, wiki pages, issue conversations, PR reviews, inline code comments — is largely invisible to product managers, support engineers, technical writers, and leadership unless they know exactly where to look. Connecting GitHub to the Glean Indexing API through tray.ai turns scattered engineering artifacts into a searchable, permission-aware knowledge base the whole company can use. Teams stop burning hours hunting for architectural decisions, onboarding documentation, or the rationale behind a specific code change. The integration also handles fine-grained permission mapping so private repositories stay visible only to authorized users in Glean, keeping security intact while actually sharing knowledge. ## Use cases ### Real-Time Repository Content Indexing Whenever code is pushed or a README is updated in GitHub, tray.ai triggers the Glean Indexing API to update or create the corresponding document entry right away. Engineers and non-engineers alike find current documentation when searching in Glean. No manual exports, no scheduled batch jobs. - Always-current documentation visible inside enterprise search - Eliminates stale content that misleads teams about system behavior - Cuts time-to-discovery for onboarding engineers exploring unfamiliar codebases ### Pull Request Knowledge Capture Pull requests contain real context: architectural rationale, code review debates, links to design documents. This workflow indexes open and merged PR titles, descriptions, and review comments into Glean so that decisions made during code review are permanently searchable. Product managers and architects can find the 'why' behind any feature without digging through GitHub timelines. - Preserves decision context that would otherwise be buried in PR history - Lets cross-functional stakeholders understand engineering rationale without asking - Speeds up incident post-mortems by making related PR discussions findable ### GitHub Issues as Searchable Knowledge Articles Bug reports, feature requests, and technical discussions in GitHub Issues are a living record of known problems and solutions. Indexing issue content — including labels, comments, and resolution notes — into Glean lets support engineers and QA teams surface known issues quickly without duplicating tickets. Indexed entries update automatically when issues are closed or re-opened. - Cuts duplicate bug reports by surfacing known issues before a ticket is filed - Lets support teams pull engineering context themselves during customer escalations - Keeps Glean search results in sync with issue lifecycle changes ### GitHub Wiki and Project Documentation Sync GitHub Wikis and repository-level documentation pages often hold internal technical runbooks and architecture guides that almost nobody outside the team ever finds. This use case continuously indexes those pages into Glean alongside content from Confluence, Notion, or other documentation platforms already there. Teams get one search experience across all documentation sources. - Unifies engineering and business documentation in one searchable interface - Stops documentation from going dark when teams forget to share wiki links - Supports multi-source search ranking so the best match surfaces first ### Automated Onboarding Knowledge Base New hires spend a surprising amount of time hunting for onboarding guides, environment setup docs, and architecture overviews scattered across repositories. Indexing targeted repos and file paths into Glean lets you build a structured onboarding search experience that surfaces the right content without anyone having to curate it manually. tray.ai watches for new onboarding-related files and indexes them automatically. - Cuts new engineer ramp-up time by making setup docs immediately findable - Takes the burden off engineering managers who keep pointing new hires to the same resources - Keeps onboarding materials current as repositories change ### Permission-Aware Private Repository Indexing Organizations with a mix of public and private repositories need access controls that actually hold in their search layer. This workflow maps GitHub team and organization permissions to Glean's permission model so users only see results from repositories they're authorized to access. tray.ai handles permission synchronization automatically whenever GitHub teams change. - Honors GitHub access controls inside Glean without manual upkeep - Allows broad enterprise search without exposing sensitive code or IP - Automatically reflects permission changes when GitHub teams are reorganized ### Cross-Repository Code Reference Indexing Large engineering organizations run across dozens or hundreds of repositories, and understanding how services interconnect is genuinely hard. Indexing repository metadata, dependency files, and architecture documentation into Glean lets platform and infrastructure teams support org-wide search across the entire service graph. Engineers find cross-service dependencies and shared libraries without manually exploring each repository. - Makes internal libraries and shared services discoverable across the org - Surfaces existing solutions before someone builds the same thing twice - Gives architecture reviews actual cross-repo search coverage ## Templates ### Index GitHub Repository Files into Glean on Push Detects push events in a GitHub repository via webhook, retrieves updated file contents, and upserts corresponding documents into the Glean Indexing API to keep enterprise search current. Connectors used: GitHub, Glean Indexing API ### Sync GitHub Issues to Glean Knowledge Index Listens for GitHub issue creation, update, and closure events and reflects those changes as indexed documents in Glean, so issue knowledge is searchable across the enterprise in real time. Connectors used: GitHub, Glean Indexing API ### Index Pull Request Discussions into Glean on Merge When a pull request is merged in GitHub, this template captures the PR title, description, review comments, and linked issues, then indexes the consolidated context into Glean as a permanent knowledge artifact. Connectors used: GitHub, Glean Indexing API ### Bulk Backfill GitHub Repository Content into Glean A one-time or scheduled bulk indexing workflow that crawls all files across specified GitHub repositories and indexes their content into Glean, building an initial or refreshed full-text search corpus. Connectors used: GitHub, Glean Indexing API ### Sync GitHub Team Permissions to Glean Datasource ACLs Propagates GitHub organization team membership changes into Glean's access control lists automatically, so private repository content in Glean stays visible only to authorized users. Connectors used: GitHub, Glean Indexing API ### Index GitHub Wiki Pages into Glean on Update Monitors GitHub repository wiki changes via the gollum webhook event and indexes updated wiki pages into Glean, keeping runbooks, architecture guides, and internal documentation findable in enterprise search. Connectors used: GitHub, Glean Indexing API ## Challenges Tray.ai solves ### GitHub API Rate Limiting During Bulk Indexing GitHub enforces strict rate limits on its REST and GraphQL APIs, and it's easy to exhaust quota during large bulk indexing runs across many repositories — especially in organizations with hundreds of repos and thousands of files. **How Tray.ai helps:** tray.ai workflows include built-in rate limit handling with configurable retry logic, exponential backoff, and request throttling. You can set concurrency limits at the workflow level and use tray.ai's queue connectors to spread large indexing jobs over time without hitting GitHub's API ceilings. ### Mapping GitHub Permissions to Glean ACL Format GitHub's permission model — organization roles, team hierarchies, repository-level access, branch protections — doesn't map cleanly to Glean's ACL schema, which makes enforcing the right access controls in Glean search results genuinely complicated. **How Tray.ai helps:** tray.ai's data transformation capabilities let you build custom logic that translates GitHub team membership and repository visibility settings into properly structured Glean ACL entries. Conditional branches handle edge cases like outside collaborators, forked repositories, and mixed-visibility repositories without custom code. ### Handling Large File Content and Binary Assets GitHub repositories regularly contain large Markdown files, Jupyter notebooks, configuration files, and binary assets that are either too large for the Glean Indexing API payload limits or just not suitable for text indexing. That requires selective filtering and content extraction before anything gets sent. **How Tray.ai helps:** tray.ai workflows can inspect file size and MIME type before fetching or indexing content, routing oversized or binary files to a separate handling path. Built-in data transformation steps can truncate, chunk, or extract relevant text sections to keep payloads within Glean's document size constraints. ### Keeping Deleted or Renamed Content Out of Glean When files are deleted, repositories are archived, or branches are removed in GitHub, the corresponding documents in Glean need to be deleted or marked inactive. Otherwise stale results keep surfacing, which is harder to track reliably than it sounds with event-driven approaches. **How Tray.ai helps:** tray.ai listens for GitHub push events that include removed file lists and repository deletion events, automatically triggering Glean Indexing API delete calls for each affected document. Scheduled reconciliation workflows can periodically compare indexed document URLs against live GitHub content and clean up orphaned entries. ### Managing Multi-Organization and Multi-Repo Scale Enterprise customers often manage content across multiple GitHub organizations, internal GitHub Enterprise Server instances, and hundreds of repositories at once. Maintaining a consistent and complete Glean index across all of that requires an orchestration layer that can actually keep up. **How Tray.ai helps:** tray.ai supports multi-tenant workflow configurations where a single automation blueprint can be parameterized per GitHub organization or repository group. Centralized logging, alerting, and workflow monitoring give platform teams full visibility into indexing health across all sources from one operations dashboard. ## Learn more - Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/ - Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/ - Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/ - Book a demo: https://tray.ai/contact/