Skip to content

Conversation

wolf99
Copy link
Contributor

@wolf99 wolf99 commented Sep 9, 2022

I have seen that the docs do not follow a uniform style of line breaking / line length.

Previously @ldennington has indicated a preference for a <80 char line limit (#668 (comment)) .

Thus this PR unifies the docs to follow an 80 char line limit. I have been fairly strict and also removed any breaks at end of sentences as that mixes the line breaking styles.

I have enabled the line length check performed by the markdown linter in the CI that was previously disabled since the linter was introduced in #668 .

@wolf99 wolf99 marked this pull request as ready for review September 9, 2022 22:39
Copy link
Contributor

@ldennington ldennington left a comment

Choose a reason for hiding this comment

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

Looks great! Thanks for your work to standardize this across our docs! 🚀

@ldennington ldennington merged commit 9393c1f into git-ecosystem:main Sep 19, 2022
@wolf99 wolf99 deleted the doc-line-length branch October 8, 2022 19:25
@ldennington ldennington mentioned this pull request Nov 3, 2022
ldennington added a commit that referenced this pull request Nov 3, 2022
Changes: - Check for broken links in documentation (#700) - Support macOS `arm64` installs via Homebrew (#798) - Validate installers before publishing (#813) - Auto-generate maintainer away notification issues (#842) - Install dotnet via Jammy feeds on Ubuntu 22.04 and greater (#839) - Access Azure storage account using service principle credentials (#851) - Update documentation to use reference-style links (#680) - Unify documentation line length (#862) - Add generic username/password UI (#871) - Bitbucket DC OAuth support (#607) - Distribute GCM as a dotnet tool (#886) - Drop `-core` suffix from entry executable #551 - Speed up build graph (#924)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

5 participants