Question

A developer creates a new, empty file named `deploy.sh` and adds a top comment: `# Wait for the database container to be healthy, then run migrations`. They trigger a Copilot completion expecting shell script commands, but instead receive a block of YAML that resembles a Docker Compose healthcheck definition. What is the MOST likely reason Copilot produced the wrong kind of output, and how should the developer adjust the prompt?

Accepted Answer

The comment described infrastructure concepts (container health, database) that biased Copilot toward YAML; adding a concrete shell signal like `#!/bin/bash` and an initial command stub steers it toward shell output.

Answer

The file extension `.sh` was ignored because Copilot only reads the comment text; the developer should rename the file to `deploy.yaml`.

Answer

Copilot never infers language from context, so the developer must open the Copilot settings and manually select 'Shell' as the completion language for this session.

Answer

The comment was too short to be a valid prompt; Copilot defaults to YAML for any comment under 100 characters until more context accumulates.