You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .markdownlint.yaml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -78,8 +78,8 @@ MD029:
78
78
MD030:
79
79
ul_single: 1
80
80
ol_single: 1
81
-
ul_multi: 3
82
-
ol_multi: 2
81
+
ul_multi: 1
82
+
ol_multi: 1
83
83
84
84
# MD031/blanks-around-fences : Fenced code blocks should be surrounded by blank lines : https://github.com/DavidAnson/markdownlint/blob/v0.33.0/doc/md031.md
Copy file name to clipboardExpand all lines: docs/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,13 +72,13 @@ export HS256_KEY="secret"
72
72
## 🔗 Related projects
73
73
74
74
- Genesis SDK is a set of tools for developing Genesis elements. You can find it [here](https://github.com/infraguys/gcl_sdk).
75
-
- Genesis DevTools it's a set oftools to manager life cycle of genesis projects. You can find it [here](https://github.com/infraguys/genesis_devtools).
75
+
- Genesis DevTools it's a set of tools to manager life cycle of genesis projects. You can find it [here](https://github.com/infraguys/genesis_devtools).
76
76
77
77
## 💡 Contributing
78
78
79
79
Contributing to the project is highly appreciated! However, some rules should be followed for successful inclusion of new changes in the project:
80
80
81
81
- All changes should be done in a separate branch.
82
82
- Changes should include not only new functionality or bug fixes, but also tests for the new code.
83
-
- After the changes are completed and **tested**, a Pull Request should be created with a clear description of the new functionality. And add one of the project maintainers as a reviewer.
83
+
- After the changes are completed and **tested**, a Pull Request should be created with a clear description of the new functionality. Add one of the project maintainers as a reviewer.
84
84
- Changes can be merged only after receiving an approve from one of the project maintainers.
0 commit comments