You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👋 Would the maintainers be interested in PRs to improve the consistency of the markdown in the gh_pages branch for Hacktoberfest? I had worked previously with thephpleague/commonmark to introduce markdownlint Action and take passes on correcting any discovered issues (Change List).
If so, I'd add usage of DavidAnson/markdownlint (JS) as it integrates with VSCode, shell environments, as well as being used by GitHub's Super-Linter Action, further reducing the CI maintenance cost.
I created a small POC of how this would integrate with the gh_pages branch as it's different than thephpleague/commonmark's docs/ directory on main. You can review the results here.
The text was updated successfully, but these errors were encountered:
👋 Would the maintainers be interested in PRs to improve the consistency of the markdown in the
gh_pages
branch for Hacktoberfest? I had worked previously with thephpleague/commonmark to introducemarkdownlint
Action and take passes on correcting any discovered issues (Change List).If so, I'd add usage of DavidAnson/markdownlint (JS) as it integrates with VSCode, shell environments, as well as being used by GitHub's Super-Linter Action, further reducing the CI maintenance cost.
I created a small POC of how this would integrate with the
gh_pages
branch as it's different than thephpleague/commonmark'sdocs/
directory onmain
. You can review the results here.The text was updated successfully, but these errors were encountered: