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: CONTRIBUTING.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ There are many ways in which you can contribute to EvoLP!
16
16
17
17
Having a clearer documentation benefits everyone. In this sense, you can help either fixing it or expanding it in multiple ways: with wording or clarification, reporting typos, adding corrections or even creating new pages on topics that could need further explanations.
18
18
19
-
The manuals are written in Markdown, and are built using [Documenter.jl](https://github.com/JuliaDocs/Documenter.jl). All the source files of the documentation can be found [here](https://github.com/ntnu-ai-lab/EvoLP.jl/tree/main/docs).
19
+
The manuals are written in Markdown, and are built using [Documenter.jl](https://github.com/JuliaDocs/Documenter.jl). All the source files of the documentation can be found at the docs [GitHub Page](https://github.com/ntnu-ai-lab/EvoLP.jl/tree/main/docs).
20
20
21
21
If your submission is small (typos or one or two sentences) then probably using GitHub's online editor is the best idea.
22
22
@@ -46,7 +46,7 @@ Contributing code is also possible via fork & pull request:
46
46
EvoLP follows the ColPrac: Contributor's Guide on Collaborative Practices for Community Packages guide from SciML.
47
47
This guide is a collection of best practices when contributing to packages.
48
48
49
-
You can read the full guide [here](https://github.com/SciML/ColPrac).
49
+
You can read the full guide at SciML's [ColPrac repository](https://github.com/SciML/ColPrac).
50
50
51
51
## Code style guidelines
52
52
@@ -55,7 +55,7 @@ You can read the full guide [here](https://github.com/SciML/ColPrac).
55
55
EvoLP follows Invenia's Blue code style guide.
56
56
This is a set of style conventions for Julia code that are based on a series of grounding documents (like Julia's own style guide and PEP8).
57
57
58
-
You can read the full guide [here](https://github.com/invenia/BlueStyle).
58
+
You can read the full guide at Invenia's [Blue Style repository](https://github.com/invenia/BlueStyle).
59
59
60
60
## Source code organisation
61
61
@@ -65,6 +65,7 @@ The following table shows how the EvoLP code is organised:
0 commit comments