root
/
gitlab-ce
mirror of https://gitlab.com/free-releases/gitlab-ce.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity
gitlab-ce/gems/gitlab-active-context
History
GitLab Bot 27211da937 Add latest changes from gitlab-org/gitlab@master 2025-07-11 21:07:14 +00:00
..
bin
…
doc Add latest changes from gitlab-org/gitlab@master 2025-06-10 03:12:18 +00:00
lib Add latest changes from gitlab-org/gitlab@master 2025-07-11 09:08:13 +00:00
spec Add latest changes from gitlab-org/gitlab@master 2025-07-08 12:11:02 +00:00
.gitignore Add latest changes from gitlab-org/gitlab@master 2025-02-03 09:11:35 +00:00
.gitlab-ci.yml Add latest changes from gitlab-org/gitlab@master 2025-05-13 15:18:03 +00:00
.rspec
…
.rubocop.yml Add latest changes from gitlab-org/gitlab@master 2025-06-10 03:12:18 +00:00
Gemfile Add latest changes from gitlab-org/gitlab@master 2025-02-27 21:07:57 +00:00
Gemfile.lock Add latest changes from gitlab-org/gitlab@master 2025-07-11 21:07:14 +00:00
README.md Add latest changes from gitlab-org/gitlab@master 2025-05-01 12:11:53 +00:00
Rakefile
…
gitlab-active-context.gemspec Add latest changes from gitlab-org/gitlab@master 2025-02-11 15:07:31 +00:00

README.md

GitLab Active Context

ActiveContext is a gem used for interfacing with vector stores like Elasticsearch, OpenSearch and Postgres with PGVector for storing and querying vectors.

How it works

See How it works.

Installation

TODO

Getting started

See Getting started.

Usage

See Usage

How to

Contributing

After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

Development guidelines

  1. Avoid adding too many changes in the monolith, keep concerns in the gem
  2. It's okay to reuse lib-type GitLab logic in the gem and stub it in specs. Avoid duplication this kind of logic into the code for long-term maintainability.
  3. Avoid referencing application logic from the monolith in the gem