Add a Dockerfile

By default, when Ellipsis writes code in response to comments, messages, and issues, it doesn’t have a way to test the code it generates. As a result, linter errors or failing tests can be common.

To fix this, you can provide a Dockerfile and a list of commands that Ellipsis can use to test the code it generates before submitting that code back to human.

For example, if you notice that Ellipsis constantly suggests code that doesn’t pass your linter, you should configure a Dockerfile and a lint command (e.g., npm run lint). Ellipsis will then attempt to lint it’s own code before opening a pull request. If the lint command fails, Ellipsis will fix the problem before moving on, or at least notify you why it wasn’t able to resolve the lint error.

In that example, your ellipsis.yaml configuration file might look like:

version: 1.3
build:
  file: "development.Dockerfile"
  commands: 
    - command: "npm run lint"
      description: "Ensures that code adheres to our team style guide and linter settings. Ignore warnings, only fix errors. Run this before submitting any code, as the team will not accept code that doesn't pass the linter."

and the Dockerfile might look like:

FROM node:22
COPY ./package.json ./package.json 
RUN npm install
COPY . . 

​

Instructions

Set up takes 5 minutes using our web UI. Open the console. Click “code” on the sidebar. Select your repository from the drop-down menu.