Skip to content
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

NEST-557: Add Markdown linting #47

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from
Open

NEST-557: Add Markdown linting #47

wants to merge 2 commits into from

Conversation

milosh-96
Copy link
Member

@milosh-96 milosh-96 commented Feb 17, 2025

This comment has been minimized.

@milosh-96
Copy link
Member Author

milosh-96 commented Feb 17, 2025

@Piedone Should I accept these words or?

@Piedone
Copy link
Member

Piedone commented Feb 18, 2025

Don't add the internal Readme-only part to the Readme. Just fix here what's common.

@milosh-96
Copy link
Member Author

Ok, so I now get these errors.

https://github.com/Lombiq/DotNest-Core-SDK/actions/runs/13381281403/job/37370164435

Should I wait for NEST-537 to be completed and then merge that or I can just manually fix them (basically copy what's done in 537 regarding versions in csproj files).

@Piedone
Copy link
Member

Piedone commented Feb 18, 2025

Ideally, we'd wait for that issue to be completed indeed, yes. If you don't want to wait, we can merge this as-is, just make sure by running markdownlint locally that there are no linting violations.

@milosh-96
Copy link
Member Author

I ran markdownlint and only error is that line lengths should be 80 chars, but that error doesn't show in actual build (both locally or in GH action). It's not a rush, but maybe we can merge because this one is completed. But whatever you think it's the best in this case.

@Piedone
Copy link
Member

Piedone commented Feb 18, 2025

We don't have that 80 chars limit configured, so I guess it's just that the local run didn't use the same config. So, it's OK.

Let's wait for Bence then, please.

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