Markdown syntax checker / parser before merge

Open
#109 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
markdown
Domain
ci-cd, documentation, tooling

Research direction

Start by reviewing the markup bug referenced in issue #107 and the repository's existing contribution or CI setup. The issue names no files, tests, checker, or parser entry point, so first determine the required Markdown validation scope and how a pre-merge check should run. Done means the identified markup problem is caught before merge.

Written by the indexing model from the issue text.

Description

improvement

Need to create a CI type checker before merge. Caught a markup bug in #107.

Dominant language
JavaScript
Stars
29.4k
Forks
3.1k
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 elsewhencode/project-guidelines

All issues in elsewhencode/project-guidelines

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.