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
+16-3Lines changed: 16 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,19 @@ This document is displayed because you either opened an issue or you want to pro
4
4
When interacting with other developers, users or anyone else from our community, please adhere to
5
5
[the OpenMS CODE OF CONDUCT](https://github.com/OpenMS/OpenMS/blob/develop/CODE_OF_CONDUCT.md)
6
6
7
+
# Setting up dev environment
8
+
Install conda/mamba (or use a venv).
9
+
Install git.
10
+
Install a C++ compiler.
11
+
12
+
```bash
13
+
git clone https://github.com/OpenMS/autowrap
14
+
cd autowrap
15
+
mamba create -n autowrap -f environment.yml
16
+
python -m pytest
17
+
```
18
+
19
+
7
20
# Reporting an Issue:
8
21
9
22
You most likely came here to:
@@ -18,10 +31,10 @@ If you found a bug, e.g. an autowrap tool crashes during code generation, it is
18
31
- how you installed autowrap (e.g., from source, pip)
19
32
- a description on how to reproduce the bug
20
33
- relevant tool output (e.g., error messages)
21
-
- data to repoduce the bug (If possible as a GitHub gist. Other platforms like Dropbox, Google Drive links also work. If you can't share the data publicly please indicate this and we will contact you in private.)
34
+
- data to reproduce the bug (If possible as a GitHub gist. Other platforms like Dropbox, Google Drive links also work. If you can't share the data publicly please indicate this and we will contact you in private.)
22
35
23
-
If you are an official OpenMS team meber:
24
-
- label your issue using github labels (e.g. as: question, defect) that indicate the type of issue and which components of autowrap (blue labels) are affected. The severity is usually assigned by OpenMS maintainers and used internally to e.g. indicate if a bug is a blocker for a new release.
36
+
If you are an official OpenMS team member:
37
+
- label your issue using GitHub labels (e.g. as: question, defect) that indicate the type of issue and which components of autowrap (blue labels) are affected. The severity is usually assigned by OpenMS maintainers and used internally to e.g. indicate if a bug is a blocker for a new release.
0 commit comments