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
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Overview
1
+
# Overview
2
2
3
3
Thank you for investing your time in contributing to our project! There are
4
4
numbers of ways to contribute to the project and we appreciate all of them. If
@@ -26,7 +26,9 @@ If you have used CppInterOp and you have particular project proposal please reac
26
26
27
27
### Submit a bug report
28
28
29
-
If something does not seem right [search if an issue already exists](https://docs.github.com/en/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests#search-by-the-title-body-or-comments) in [CppInterOps issue tracker](https://github.com/compiler-research/CppInterOp/issues). If a related issue doesn't exist, you can open a new issue using a relevant [issue form](https://github.com/compiler-research/CppInterOp/issues/new).
29
+
If something does not seem right [search if an issue already exists](https://docs.github.com/en/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests#search-by-the-title-body-or-comments)
30
+
in [CppInterOps issue tracker](https://github.com/compiler-research/CppInterOp/issues). If a related issue doesn't exist, you can open a
31
+
new issue using a relevant [issue form](https://github.com/compiler-research/CppInterOp/issues/new).
30
32
31
33
### Good first issues
32
34
@@ -66,7 +68,7 @@ review quickly and successfully share several common traits:
66
68
is a guideline about how write good code comments. [Here](https://stackoverflow.com/questions/184618/what-is-the-best-comment-in-source-code-you-have-ever-encountered)
67
69
are examples of what *not* to write as a code comment.
68
70
69
-
### Developer Documentation
71
+
### Developer Documentation
70
72
71
73
We have documented several useful hints that usually help when addressing issues
72
-
as they come during developement time in our [developer documentation](https://cppinterop.readthedocs.io/en/latest/InstallationAndUsage.html).
74
+
as they come during developement time in our [developer documentation](https://cppinterop.readthedocs.io/en/latest/InstallationAndUsage.html).
0 commit comments