Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Syntax highlight error: Did not highlight comment after string value

Open
#531 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, yaml
Domain
tooling

Research direction

Start with the YAML reproduction in the issue and verify the behavior using the extension version v1.28.1 in VS Code. Trace the syntax-highlighting behavior for the inline comment after the quoted value; done means the # Cache causes errors on macOS text is highlighted as a comment.

Written by the indexing model from the issue text.

Description

bug

Describe the bug

In the screenshot below, the comment # Cache causes errors on macOS wasn't highlighted as comment.

screenshot
      - name: Cache
        uses: actions/cache@v4
        timeout-minutes: 2
        continue-on-error: true
        if: matrix.os != 'macos-latest' # Cache causes errors on macOS
        with:
          path: |
            ~/.cargo
            target
          key: ${{ github.job }}-${{ runner.os }}-${{ hashFiles('rust-toolchain') }}-${{ hashFiles('**/Cargo.lock') }}
          restore-keys: |
            ${{ github.job }}-${{ runner.os }}-${{ hashFiles('rust-toolchain') }}-${{ hashFiles('**/Cargo.lock') }}
            ${{ github.job }}-${{ runner.os }}-${{ hashFiles('rust-toolchain') }}-

To Reproduce

Already provided

Expected behavior

Highlight comment as comment

Screenshots

Already provided

Extension Version
v1.28.1

Additional context
Add any other context about the problem here.

Dominant language
TypeScript
Stars
661
Forks
214
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/vscode-github-actions

All issues in github/vscode-github-actions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.