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
Fix build issues #44
Fix build issues #44
Conversation
This is the result of running `composer update --lock` to avoid having composer complaining about outdated lockfile. Signed-off-by: Luís Cobucci <lcobucci@gmail.com>
These files are there for legacy purposes only and are just redirecting users. They don't need to be validated. Signed-off-by: Luís Cobucci <lcobucci@gmail.com>
b474116
to
b1f3ef6
Compare
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 content of the section on installation has also been revised, but is now misleading. Why "installation", keys are generated here. But what should the user do to reach the goal?
Maybe this should be handled in a separate pull request.
Making sure we follow the rule `MD025/single-title/single-h1`. Signed-off-by: Luís Cobucci <lcobucci@gmail.com>
Signed-off-by: Luís Cobucci <lcobucci@gmail.com>
47ed183
to
a589d8d
Compare
@froschdesign I dropped the commits that changed the rules you rejected. After reviewing the failures on #43 it's quite likely that I was wrong and mixed up the reported issues on my local env and CI. |
Yeah... I was wrong. Sorry about the confusion 😄 |
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.
👍
Description
This makes sure our documentation is compatible with markdownlint rules so that #43 can focus on the right stuff.