GitLab

Dropstone integrates with your GitLab workflow through your GitLab CI/CD pipeline or with GitLab Duo.

In both cases, Dropstone will run on your GitLab runners.

GitLab CI

Dropstone works in a regular GitLab pipeline. You can build it into a pipeline as a CI component

Here we are using a community-created CI/CD component for Dropstone: nagyv/gitlab-dropstone.

Features

• Use custom configuration per job: Configure Dropstone with a custom configuration directory, for example ./config/#custom-directory to enable or disable functionality per Dropstone invocation.
• Minimal setup: The CI component sets up Dropstone in the background, you only need to create the Dropstone configuration and the initial prompt.
• Flexible: The CI component supports several inputs for customizing its behavior

Setup

1. Store your Dropstone authentication JSON as a File type CI environment variables under Settings > CI/CD > Variables. Make sure to mark them as "Masked and hidden".

2. Add the following to your .gitlab-ci.yml file.

   include:
     - component: $CI_SERVER_FQDN/nagyv/gitlab-dropstone/dropstone@2
       inputs:
         config_dir: ${CI_PROJECT_DIR}/dropstone-config
         auth_json: $DROPSTONE_AUTH_JSON # The variable name for your Dropstone authentication JSON
         command: optional-custom-command
         message: "Your prompt here"
   

For more inputs and use cases check out the docs for this component.

GitLab Duo

Dropstone integrates with your GitLab workflow. Mention @dropstone in a comment, and Dropstone will execute tasks within your GitLab CI pipeline.

Features

• Triage issues: Ask Dropstone to look into an issue and explain it to you.
• Fix and implement: Ask Dropstone to fix an issue or implement a feature. It will create a new branch and raise a merge request with the changes.
• Secure: Dropstone runs on your GitLab runners.

Setup

Dropstone runs in your GitLab CI/CD pipeline, here's what you'll need to set it up:

1. Configure your GitLab environment
2. Set up CI/CD
3. Get a Dropstone API key (see Quickstart)
4. Create a service account
5. Configure CI/CD variables
6. Create a flow config file. Example:

image: node:22-slim
commands:
  - echo "Installing Dropstone"
  - curl -fsSL https://dropstone.io/install | bash
  - echo "Installing glab"
  - export GITLAB_TOKEN=$GITLAB_TOKEN_DROPSTONE
  - apt-get update --quiet && apt-get install --yes curl wget gpg git && rm --recursive --force /var/lib/apt/lists/*
  - curl --silent --show-error --location "https://raw.githubusercontent.com/upciti/wakemeops/main/assets/install_repository" | bash
  - apt-get install --yes glab
  - echo "Configuring glab"
  - echo $GITLAB_HOST
  - echo "Creating Dropstone auth configuration"
  - mkdir --parents ~/.local/share/dropstone
  - |
    cat > ~/.local/share/dropstone/auth.json << EOF
    {
      "dropstone": {
        "type": "api",
        "key": "$DROPSTONE_API_KEY"
      }
    }
    EOF
  - echo "Configuring git"
  - git config --global user.email "dropstone@gitlab.com"
  - git config --global user.name "Dropstone"
  - echo "Testing glab"
  - glab issue list
  - echo "Running Dropstone"
  - |
    dropstone run "
    You are an AI assistant helping with GitLab operations.

    Context: $AI_FLOW_CONTEXT
    Task: $AI_FLOW_INPUT
    Event: $AI_FLOW_EVENT

    Please execute the requested task using the available GitLab tools.
    Be thorough in your analysis and provide clear explanations.

    Use the glab CLI to access data from GitLab. The glab CLI is already authenticated.

    If you are asked to summarize an MR or issue, or provide more information,
    post back a note to the MR/Issue so the user can see it.
    "
  - git checkout --branch $CI_WORKLOAD_REF origin/$CI_WORKLOAD_REF
  - echo "Checking for git changes and pushing if any exist"
  - |
    if ! git diff --quiet || ! git diff --cached --quiet || [ -n "$(git ls-files --others --exclude-standard)" ]; then
      echo "Git changes detected, adding and pushing..."
      git add .
      if git diff --cached --quiet; then
        echo "No staged changes to commit"
      else
        echo "Committing changes to branch: $CI_WORKLOAD_REF"
        git commit --message "Dropstone changes"
        echo "Pushing changes up to $CI_WORKLOAD_REF"
        git push "https://gitlab-ci-token:$GITLAB_TOKEN@$GITLAB_HOST/$CI_PROJECT_PATH.git" $CI_WORKLOAD_REF
        echo "Changes successfully pushed"
      fi
    else
      echo "No git changes detected, skipping push"
    fi
variables:
  - DROPSTONE_API_KEY
  - GITLAB_TOKEN_DROPSTONE
  - GITLAB_HOST

You can refer to the GitLab Duo Agent Platform docs for detailed instructions.

Examples

Here are some examples of how you can use Dropstone in GitLab.

• Explain an issue

  Add this comment in a GitLab issue.

  @dropstone explain this issue
  

  Dropstone will read the issue and reply with a clear explanation.

• Fix an issue

  In a GitLab issue, say:

  @dropstone fix this
  

  Dropstone will create a new branch, implement the changes, and open a merge request with the changes.

• Review merge requests

  Leave the following comment on a GitLab merge request.

  @dropstone review this merge request
  

  Dropstone will review the merge request and provide feedback.