-
Notifications
You must be signed in to change notification settings - Fork 9.1k
vallidate-markdown failure: How should we maintain scripts across branches? #3542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
That's a fun problem. I have a horrible feeling that it really means we should split the repo into tools and specs ... But for now I'm happy to commit to cherry pick the tools changes into the active branches of that's useful? (Make me an issue if we choose this outcome) |
@baywet I was looking at cherry-picking changes to |
You can safely include the changes I've made in the labelling automations. It only runs from main. |
@handrews - noted the version of node (used in the GitHub action)is quite old. I also opened an issue against the mdv repo asking how to display line numbers where a syntax issue occurs. |
If someone wants to update things that can be a separate issue/PR. I'm just trying to clear out all of the things that are broken, and all of the things that are blocked from merging because of broken things. |
The validate-markdown check is currently failing on all branches but main because main now has a very different JavaScript configuration from the branches. Those branches should have GitHub actions that match their environments, but currently on v3.1.1-dev and v3.2.0-dev, the JavaScript package that validate-markdown runs fails even if you just ask it for help output:
The text was updated successfully, but these errors were encountered: