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
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,14 +6,17 @@ When contributing to this repository, please first discuss the changes you wish
6
6
7
7
### Reporting bugs or making feature requests
8
8
9
-
You can use the [Issues](https://github.com/linkml/linkml-runtime/issues) tab to create bug and feature requests. Providing enough details to the developers to verify and troubleshoot your issue is paramount:
9
+
To report a bug or suggest a new feature, please go to the [linkml/linkml issue tracker](https://github.com/linkml/linkml/issues), as we are
10
+
consolidating issues there.
11
+
12
+
Please supply enough details to the developers to enable them to verify and troubleshoot your issue:
10
13
11
14
* Provide a clear and descriptive title as well as a concise summary of the issue to identify the problem.
12
15
* Describe the exact steps which reproduce the problem in as many details as possible.
13
16
* Describe the behavior you observed after following the steps and point out what exactly is the problem with that behavior.
14
17
* Explain which behavior you expected to see instead and why.
15
18
* Provide screenshots of the expected or actual behaviour where applicable.
16
-
* Tag the issue with appropriate label names. For ex., if your issue is about a bug that needs to be fixed in the repo, tag the issue with the `bug` label from the list of [labels](https://github.com/linkml/linkml-runtime/labels). If an appropriate label name doesn't exist, create one, with a name that clearly encapsulates the topic of the issue.
19
+
* Tag the issue with appropriate label names. For example, if your issue is about a bug that needs to be fixed in the repo, tag the issue with the `bug` label from the list of [labels](https://github.com/linkml/linkml-runtime/labels). If an appropriate label doesn't exist, create one, with a name that clearly encapsulates the topic of the issue.
17
20
18
21
### The development lifecycle
19
22
@@ -24,6 +27,8 @@ You can use the [Issues](https://github.com/linkml/linkml-runtime/issues) tab to
24
27
25
28
Note: All the development must be done on a branch on your fork.
26
29
30
+
ALSO NOTE: github.com lets you create a pull request from the main branch, automating the steps above.
31
+
27
32
> A code review (which happens with both the contributor and the reviewer present) is required for contributing.
0 commit comments