[docs-verifier] False positive broken link for casing mismatch in file name

Open
#401 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
tooling

Research direction

Start with the docs-verifier broken-link check and compare its behavior with the casing-mismatch example in PR #42408's linked discussion. Done means a filename casing mismatch is no longer reported as a broken link while genuinely broken links remain detected.

Written by the indexing model from the issue text.

Description

For example, these two files had upper case characters in their names: https://github.com/dotnet/docs/pull/42408#discussion_r1742166111

Dominant language
C#
Stars
27
Forks
43
Avg merge
12h 33m
Merged PRs (30d)
26

Contributor guide

No contributing guide indexed for this repository

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 dotnet/docs-tools

All issues in dotnet/docs-tools

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.