Skip to content

Separate Calling of `gitlab-code-completion` and `gitlab-code-generation`

What does this merge request do and why?

Right now we call gitlab-code-creation and provide an intent flag set to either "generation" or "completion". It has been decided by the team that this is not a clear way to handle this distinction.

Note: This will not complete the work on #274 (closed) but is a first step toward that end.

The Goal

I user should be able to create a config and specify with ease an clarity a different "model" for calling generation or completion when trying call the gitlab endpoint for code-suggestions.

The two models will be named accordingly

  • gitlab-code-completion
  • gitlab-code-generation

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Merge request checklist

  • I've ran the affected pipeline(s) to validate that nothing is broken.
  • Tests added for new functionality. If not, please raise an issue to follow up.
  • Documentation added/updated, if needed.

Link: #274 (closed)

Edited by Stephan Rayner

Merge request reports