General Discussions

Please add a supported GitHub connector mechanism to index file body/content by exact filename or filename pattern, not only by file extension.

The current GitHub content-selection logic is extension-based. It builds the body-indexing allowlist from 

, then fetches content only when the filename ends with one of those allowed extensions; otherwise it returns 

The public GitHub Server connector docs align with this behavior: content indexing is limited to specific text/Markdown and code/configuration file extensions.

As a result, extensionless files such as 

 can be crawled at the repository level, but their body/content is not eligible for indexing under the current documented and implemented behavior.

Some customers store meaningful config or workflow files in extensionless filenames. Today those files may still surface as metadata/path, but not as indexed body content, which limits search, retrieval, and downstream code/content understanding for those files.

This creates a gap when the source repository uses valid operational file naming conventions that do not end in a standard extension.

Add one of the following supported controls for GitHub body/content indexing:

fileNamesToIndexBody = BogieFile,Jenkinsfile,Dockerfile

Filename-pattern allowlist, for example regex or glob support, for exact operational filenames that do not have extensions.

The key requirement is that customers can opt specific extensionless filenames into body indexing without broadly enabling unsupported file types or requiring repository-side renames.

A GitHub datasource admin can explicitly allow body indexing for one or more extensionless filenames.

Allowed extensionless filenames have content fetched and indexed during normal Git/content crawl processing.

Existing extension-based controls continue to work unchanged for standard file types.

Unlisted extensionless files remain unchanged and do not get body-indexed by default.

The behavior is documented clearly so support can distinguish repo crawl scope from file body-indexing eligibility.

Feature Request - GitHub connector: support filename-based body indexing for extensionless files

Home

Forum

Events

Content

Courses

Collections

People

Contributors

Albums

Groups

Chat

Channels

Tools

Help

Welcome to the Gleaniverse. Empowering work with AI. Connected by knowledge. Growing together. Search Where would you like to start? Join the discussions.

Glean Community

Gleaniverse Community

Copyright

Terms of Service

Privacy Policy

Code of Conduct

Your Privacy Choices

It looks like there is no account associated with the email you provided. The event is for members only. Please complete the application to join our community first.

Thank you for your interest in joining us

Thanks for your interest in joining the event. However, your account is still pending. Once it's approved, you'll be able to register for the event. Please contact us via community@glean.com if you need support.

Pending Approval

Login to the Glean Community to connect with others, attend community events, and more!

Login or Sign Up for even more

To unlock all parts of the community and get the best experience, complete your profile.

Hey, complete your profile

It looks like there is no account associated with the email you provided. Please complete the application to join our community.

Thank you for your interest in joining Glean Community.

Thanks for your interest in joining Glean Community. We will review your request shortly and email you once it's approved. Meanwhile, please feel free to contact us via community@glean.com for any questions.