-
Notifications
You must be signed in to change notification settings - Fork 9
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
Document signing of Git Commits #33
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small nitpicks.
Co-authored-by: Dominik Gedon <[email protected]>
Co-authored-by: Dominik Gedon <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The list layout is still "broken", but it's fine. We have more Markdown issues in the README.
Thank you, Julio.
What's broken? I see it correctly on the GitHub preview. |
BTW @nodeg, if we really want to enforce such rules, there should be actions telling the users about that (at every repo where there're markdown files :-)) In the end we are talking about linting, not about syntax users, and most contributors (myself included), are not really aware of all those rules, and won't remember about them for casual contributions. |
Makes sense. An idea would be to have a GitHub Actions for linting Markdown files when opening a Pull Request. |
No description provided.