|
1 | 1 | # Contributing guidelines |
2 | 2 |
|
3 | | -We welcome any kind of contribution to `imas-python`, |
| 3 | +We welcome any kind of contribution to `IMAS-Python`, |
4 | 4 | from a simple comment, a question or even a full fledged pull |
5 | 5 | request. |
6 | 6 | Please first make sure you read and follow the |
7 | 7 | [Code of Conduct](CODE_OF_CONDUCT.md). |
8 | 8 |
|
9 | 9 | ## You think you found a bug in the code, or have a question in its use |
10 | | -1. use the [issue search](https://github.com/iterorganization/imas-python/issues) |
| 10 | +1. use the [issue search](https://github.com/iterorganization/IMAS-Python/issues) |
11 | 11 | to check if someone already created a similar issue; |
12 | 12 | 3. if not, make a **new issue** to describe your problem or question. |
13 | 13 | In the case of a bug suspiscion, please try to give all the relevant |
14 | 14 | information to allow reproducing the error or identifying |
15 | | -its root cause (version of the imas-python, OS and relevant |
| 15 | +its root cause (version of the IMAS-Python, OS and relevant |
16 | 16 | dependencies, snippet of code); |
17 | 17 | 4. apply relevant labels to the issue. |
18 | 18 |
|
19 | 19 | ## You want to make or ask some change to the code |
20 | | -1. use the [issue search](https://github.com/iterorganization/imas-python/issues) |
| 20 | +1. use the [issue search](https://github.com/iterorganization/IMAS-Python/issues) |
21 | 21 | to check if someone already proposed a similar idea/change; |
22 | 22 | 3. if not, create a **new issue** to describe what change you would like to see |
23 | 23 | implemented and specify it if you intend to work on it yourself or if some help |
|
0 commit comments