https://github.com/sourcegraph/extension-api-classes
Classes used by the Sourcegraph extension API
https://github.com/sourcegraph/extension-api-classes
Last synced: 4 days ago
JSON representation
Classes used by the Sourcegraph extension API
- Host: GitHub
- URL: https://github.com/sourcegraph/extension-api-classes
- Owner: sourcegraph
- License: mit
- Created: 2019-04-29T11:25:03.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2026-03-03T19:08:29.000Z (12 days ago)
- Last Synced: 2026-03-03T22:59:07.941Z (12 days ago)
- Language: TypeScript
- Size: 551 KB
- Stars: 2
- Watchers: 50
- Forks: 1
- Open Issues: 38
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# @sourcegraph/extension-api-classes
[](https://www.npmjs.com/package/@sourcegraph/extension-api-classes)
[](https://www.npmjs.com/package/@sourcegraph/extension-api-classes)
[](https://travis-ci.org/sourcegraph/extension-api-classes)
[](https://codecov.io/gh/sourcegraph/extension-api-classes)
[](https://github.com/prettier/prettier)
[](https://github.com/semantic-release/semantic-release)
## ⚠️ Deprecation notice
**Sourcegraph extensions have been deprecated with the September 2022 Sourcegraph
release. [Learn more](https://docs.sourcegraph.com/extensions/deprecation).**
The repo and the docs below are kept to support older Sourcegraph versions.
## Description
Classes used by the Sourcegraph extension API
## Install
```
npm install @sourcegraph/extension-api-classes
# or
yarn add @sourcegraph/extension-api-classes
```
## Build
```
yarn
yarn build
```
## Test
```
yarn test
```
## Release
Releases are done automatically in CI when commits are merged into master by analyzing [Conventional Commit Messages](https://conventionalcommits.org/).
After running `yarn`, commit messages will be linted automatically when committing though a git hook.
The git hook can be circumvented for fixup commits with [git's `fixup!` autosquash feature](https://fle.github.io/git-tip-keep-your-branch-clean-with-fixup-and-autosquash.html), or by passing `--no-verify` to `git commit`.
You may have to rebase a branch before merging to ensure it has a proper commit history, or squash merge with a manually edited commit message that conforms to the convention.