Skip to main content

​
Overview

If your policies, runbooks, and product documentation live in GitLab, you can make them answerable in Wolfia directly from the source. You pick the projects, branches, and files to include, and Wolfia keeps its knowledge base in step with the project as files change. GitLab synced files in the Knowledge Hub

​
What we sync

  • Documentation files - Markdown (.md, .mdx), plain text, HTML, and JSON
  • Office documents - Word (.docx, .doc), Excel (.xlsx, .xlsm, .xls), PowerPoint (.pptx), and CSV
  • PDFs - Policy documents, reports, and attestations
  • Images - PNG, JPG, and WebP diagrams such as architecture overviews
  • Email files - .eml messages saved into the project
The connection is read-only. Wolfia never writes to your projects.

​
Prerequisites

  • A GitLab.com account with membership in the projects you want to sync
  • Admin role in Wolfia to connect the integration

​
Setup instructions

1

Connect GitLab

Navigate to Knowledge Hub in the left sidebar, find the GitLab integration, and click Connect. Sign in to GitLab and authorize Wolfia when prompted. Wolfia requests read-only access to your projects.
2

Select projects and branches

Click Manage projects, pick the projects to sync, and choose the branch to read from for each one.Manage GitLab projects dialog
3

Pick the files to include

Browse the project file tree and select the folders and files to bring into your knowledge base. Only supported file types are selectable. Checking a folder includes every supported file under it, now and in the future.Choosing files and folders to sync
4

Sync

Click Sync now to run the first sync. Files appear in the Knowledge Hub with their project paths, grouped into folders such as Policies and Certifications & Audit Reports as they are classified.

​
How syncing works

  • Automatic refresh - Synced projects refresh once a day, so answers reflect your latest committed documentation.
  • Only changes are re-processed - Sync now and the daily refresh compare each file against the version already synced. Unchanged files are skipped, so syncs stay fast even in large projects.
  • Deletions are honored - When a synced file is removed from the project, its content is removed from your knowledge base on the next sync.
  • Facts are extracted automatically - After a file syncs, Wolfia extracts the facts it contains so they can be used in questionnaire answers, chat, and RFP responses.

​
Good practices

  • Sync from your default branch so the knowledge base always reflects reviewed, merged content.
  • Keep customer-facing documentation in dedicated folders (for example docs/policies/, docs/security/) and select those folders rather than the whole project.
  • Use descriptive file names. The file path is shown in the Knowledge Hub and helps your team find sources quickly.

​
FAQ

Markdown, MDX, plain text, HTML, JSON, PDF, Word, Excel, PowerPoint, CSV, PNG, JPG, WebP, and EML files are supported. Unsupported file types do not appear in the file picker.
Wolfia only syncs the files you explicitly select. If you select only documentation folders, source code is never read into the knowledge base.
Wolfia checks the selected files against the project and re-processes only the files that changed since the last sync. Files that are unchanged are skipped.
Click Disconnect on the GitLab page in the Knowledge Hub. You can also revoke the authorization from your GitLab applications settings.

GitHub integration

Sync documentation from GitHub repositories the same way.

Knowledge base

How Wolfia organizes and uses your synced knowledge.

Adding knowledge

Other ways to bring content into Wolfia.

SharePoint integration

Sync documents from SharePoint sites.