Automattic / Automattic/harper

Commit IDs should not be spell checked

Open
#3,557 2 comments 1 reaction 0 assignees View on GitHub
bug harper-comments harper-core linting
Dominant language
Rust
Stars
15.4k
Forks
627
Avg merge
1d 15h
Merged PRs (30d)
102

Description

**What got flagged?**
77eb1817c797407ecd0fa2da4a6c43e723b892e3

**Why is this incorrect?**
This is a git commit ID, and there's nothing to spell check here. This is probably not trivial to detect but there could be some heuristics, e.g., based on length or the fact that only hex digits are used.

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by locating the spell-checking path that flags the example commit ID and inspect how token text is classified; done means commit IDs such as 77eb1817c797407ecd0fa2da4a6c43e723b892e3 are ignored without suppressing ordinary spell-checking, with regression coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, rust
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.