New lint for markdown in the title and/or description
Open
Nobody has claimed this yet.
in discussion
- Dominant language
- Rust
- Stars
- 34
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Pretty self-explanatory. It's not supported by Jekyll (or vitepress, to my knowledge)
Originally posted by @Pandapip1 in https://github.com/ethereum/EIPs/pull/6789#pullrequestreview-1369068439
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name any files, tests, or entry points. Start by locating the existing lint implementations and the validation path for issue titles and descriptions. Confirm which Markdown constructs are unsupported by Jekyll or VitePress, then define tests that show the lint rejects them and accepts supported content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jekyll, markdown, rust
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100