Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>CODEOWNERS for GitLabNew to Visual Studio Code? Get it now.
CODEOWNERS for GitLab

CODEOWNERS for GitLab

ovcharik

|
2 installs
| (0) | Free
Syntax highlighting and code owners info for GitLab CODEOWNERS files
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

CODEOWNERS for GitLab (VS Code extension)

VS Code extension with support for GitLab CODEOWNERS files.

Features

  • File type detection — CODEOWNERS files are recognized as codeowners language, so formatting and linting tools (e.g. ESLint with a custom parser) can be configured to validate them via eslint.validate.

  • Syntax highlighting — highlights sections [Section] (including optional ^[Section]), patterns, owners (@user, @group/subgroup, emails), optional owners and approval counts.

  • Status bar — shows the code owners of the currently open file. Hover to see details (section, optional). Click to open a quick pick with all owners (selecting one copies its name to the clipboard).

    Status bar showing code owners of the open file

  • Section folding — sections fold from their header to the next section; trailing blank lines and comments stay visible so they remain attached to the section that follows.

  • GitLab search semantics — search paths: CODEOWNERS, docs/CODEOWNERS, .gitlab/CODEOWNERS; patterns, sections, and optional/hidden sections follow GitLab's matching rules (last match wins, section composition).

Zero runtime dependencies — parsing is done in-house, without @gitlab/codeowners.

Commands

Command Description
CODEOWNERS for GitLab: Show owners of current file Quick pick list of all code owners for the active file
CODEOWNERS for GitLab: Search files by owner List all files owned by a given owner (user, group or email)

Show owners of current file

Quick pick with all code owners of the active file

Search files by owner

File list resulting from a search by owner

Development

npm install
npm run compile      # type check + bundle (vite, CJS single file)
npm run watch:vite   # rebuild on change (dev)
npm run watch:tsc    # type check on change (dev)
npm test             # vitest unit tests
npm run lint         # oxlint
npm run fmt          # oxfmt
npm run package      # build for publishing

Limitations

  • Multi-root workspaces: only the first workspace folder is scanned
  • Character classes in patterns (*.[ch]) are matched literally

License

MIT

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft