Skip to content

Conversation

Jeymz
Copy link
Contributor

@Jeymz Jeymz commented Sep 12, 2025

  • Updated package.json to include separate linting scripts for ESLint and MarkdownLint.
  • Added fix options for both ESLint and MarkdownLint.
  • Included markdownlint-cli as a dependency.
  • Created a linting workflow to check both markdown & eslint. (Feel free to remove this)

Reasoning: Because I take clean markdown very seriously 🤣

- Updated package.json to include separate linting scripts for ESLint and MarkdownLint.
- Added fix options for both ESLint and MarkdownLint.
- Included markdownlint-cli as a dependency.
{
"name": "@benborla29/mcp-server-mysql",
"version": "2.0.5",
"name": "@bulgariamitko/mcp-server-mysql-write",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I am assuming this was due to a change in the name from the package.json file, but both may need to be set back to the original. Seems a little risky to me to be changing this.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I went ahead and reverted. Looks like this was change in PR #77

Copy link
Contributor

Choose a reason for hiding this comment

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

@Jeymz yeah that was actually my mistake I already mention it in the merge - #77

Copy link
Contributor

Choose a reason for hiding this comment

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

@Jeymz I fixed that with this pull request - #87

…ackage-lock.json

- Reverting package name & description to original author in `package.json` and `package-lock.json`
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Feel free to remove this workflow. Would love to see markdown lint checks, but don't want to hold up the build pipeline due to failure.

@Jeymz
Copy link
Contributor Author

Jeymz commented Oct 16, 2025

@benborla Is this something you can look at, or do you want me to close this PR?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants