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

Exclude generated *.lock.yml workflow files from spelling checks

Closed Beginner friendly
#6,547 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions
Domain
ci-cd, tooling

Research direction

Start in .github/workflows/ and inspect the Check Spelling workflow using check-spelling/check-spelling@v0.0.26. Confirm how it selects files, then exclude generated *.lock.yml files under .github/workflows/ and verify that spell-check reports no longer include those artifacts.

Written by the indexing model from the issue text.

Description

Needs-Triage
Relevant area(s)

WinGet CLI

Relevant command(s)

N/A — repository validation tooling

Brief description of your issue

The Check Spelling workflow scans generated *.lock.yml workflow files under .github/workflows/. These files are compiled output (e.g. from GitHub Agentic Workflows) and contain many third-party/tooling terms (openai, claude, gpt, zizmor, certificate-authority names, etc.) that are not part of the source content authors write, causing unrelated pull requests to fail spell check with a large batch of unrecognized words. Alternatively, I've also seen warnings that the lock files don't parse in time causing excess warnings that really aren't necessary.

Steps to reproduce
  1. Open a pull request that touches any file in the repository.
  2. Observe the Check Spelling workflow run and report comment.
  3. Note unrecognized words originating from .github/workflows/*.lock.yml files (e.g. issue-closure-recommendation.lock.yml) rather than from the actual changed files.
Expected behavior

*.lock.yml files under .github/workflows/ are excluded from spell checking, since they are generated artifacts rather than authored content.

Actual behavior

The Check Spelling workflow scans *.lock.yml files and reports dozens of unrecognized words unrelated to the pull request's actual changes.

Environment
GitHub Actions
check-spelling/check-spelling@v0.0.26
microsoft/winget-cli master
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
2d 12h
Merged PRs (30d)
21

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 microsoft/winget-cli

All issues in microsoft/winget-cli

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.