- Issue created by @kburakozdemir
- 🇺🇸United States DamienMcKenna NH, USA
The d.o documentation guidelines → call for two blank lines before headings, so all of the no-multiple-lines messages are incorrect.
I would be happy to commit the ul-styles changes, if you want to do a merge request of just that?
BTW the "assigned" field is for indicating you're actively working on an issue, it isn't for indicating that you worked on an issue and are asking for attribution; when you're finished with your work on an issue please set the "assigned" field to "Unassigned". Thank you.
- 🇹🇷Turkey kburakozdemir İstanbul
kburakozdemir → changed the visibility of the branch 3480290-fix-readme-ul-styles to hidden.
- 🇹🇷Turkey kburakozdemir İstanbul
hi, thanks for your response. your comments and guidance is very much appreciated.
I would like to correct the ul-styles however I would like to ask something before proceeding:
In the guidelines, it says "Two lines prior to ##/### headings", however there is a ### heading that does not have 2 lines before it. Is it because it is the first line after ## heading (there is no paragraph between them). Should I also correct it or is it OK?
- 🇹🇷Turkey kburakozdemir İstanbul
kburakozdemir → changed the visibility of the branch 3480290-fix-readme.md-linting to hidden.
- 🇺🇸United States DamienMcKenna NH, USA
I think it's ok to skip the two line requirement for the "Advanced usage" section because there's no text between the second level and third level headings.
- Merge request !147Fix ul style and delete extra line before heading → (Open) created by kburakozdemir
- 🇪🇸Spain fjgarlin
@kburakozdemir - note that creating the same issue in multiple projects can be penalized as it might be seen as credit farming and trying to chase easy contribution credits.
Rather than opening the same issue in multiple modules, it would be more helpful to maybe collaborate in the
gitlab_templatesproject, as these issues are not even picked up by the GitLab CI system. Or even better, help in the "Coding Standards" side of things to agree on format and rules first. See https://www.drupal.org/docs/develop/coding-standards/markdown-coding-sta... → . That'd need to get sorted before any lint tools should be considered for the standard pipeline.I'd encourage to close this issue and then work on the right places where it could have a wider impact.