|
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 |
| -3. if not, make a **new issue** to describe your problem or question. |
| 12 | +2. 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 |
| -4. apply relevant labels to the issue. |
| 17 | +3. 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 |
| -3. if not, create a **new issue** to describe what change you would like to see |
| 22 | +2. 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
|
24 | 24 | will be needed;
|
25 |
| -4. wait until some kind of consensus is reached about your idea being relevant, |
| 25 | +3. wait until some kind of consensus is reached about your idea being relevant, |
26 | 26 | at which time the issue will be assigned (to you or someone else who can work on
|
27 | 27 | this topic);
|
28 |
| -5. if you do the development yourself, fork the repository to your own Github |
| 28 | +4. if you do the development yourself, fork the repository to your own Github |
29 | 29 | profile and create your own feature branch off of the latest develop commit.
|
30 | 30 | Make sure to regularly sync your branch with the latest commits from `develop`
|
31 | 31 | (find instructions
|
32 | 32 | [here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork));
|
33 |
| -6. when your development is ready, create a pull request (find instructions |
| 33 | +5. when your development is ready, create a pull request (find instructions |
34 | 34 | [here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)).
|
35 | 35 |
|
36 | 36 |
|
|
0 commit comments