Skip to content

Add remark-lint-visimark to plugin list - #1504

Open
michal-niedzwiedzki wants to merge 2 commits into
remarkjs:mainfrom
michal-niedzwiedzki:add-remark-lint-visimark
Open

michal-niedzwiedzki wants to merge 2 commits into
remarkjs:mainfrom
michal-niedzwiedzki:add-remark-lint-visimark

Conversation

@michal-niedzwiedzki

@michal-niedzwiedzki michal-niedzwiedzki commented Oct 5, 2026 •

Copy link
Copy Markdown

Initial checklist

  • I read the support docs
  • I read the contributing guide
  • I agree to follow the code of conduct
  • I searched issues and discussions and couldn’t find anything or linked relevant results below
  • I made sure the docs are up to date
  • I included tests (or that’s not needed)

Description of changes

Adds remark-lint-visimark to the list of plugins in doc/plugins.md. It is a unified plugin with a default export, the remark-plugin keyword in package.json, and the remark-plugin topic on its repo. (The npm package is remark-lint-visimark; it lives in the packages/remark-visimark folder of the monorepo.)

@github-actions github-actions Bot added the 👋 phase/new Post is being triaged automatically label Oct 5, 2026
@github-actions

This comment has been minimized.

@codecov

codecov Bot commented Oct 5, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (1146b3a) to head (4acbf22).

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #1504   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            6         6           
  Lines          138       138           
=========================================
  Hits           138       138           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@remcohaszing remcohaszing left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This points to a 404 page. Is the project private?

Updated the URL for the remark-lint-visimark plugin to point to the master branch.

Signed-off-by: Michał Niedźwiedzki <michal@epsi.pl>
@michal-niedzwiedzki

Copy link
Copy Markdown
Author

Thanks for catching this. The link was wrong: I'd used tree/main/..., but the default branch is master, so it 404'd. The repo is public. The entry now links to https://github.com/michal-niedzwiedzki/visimark/tree/master/packages/remark-visimark, which resolves. (The folder is remark-visimark; the npm package is remark-lint-visimark.)

I've also updated the PR description to follow the template. Could you take another look?

@github-actions github-actions Bot added 🤞 phase/open Post is being triaged manually and removed 👋 phase/new Post is being triaged automatically labels Oct 20, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🤞 phase/open Post is being triaged manually

Development

Successfully merging this pull request may close these issues.

2 participants