@@ -9,28 +9,28 @@ Please first make sure you read and follow the
99## You think you found a bug in the code, or have a question in its use
10101 . use the [ issue search] ( https://github.com/iterorganization/IMAS-Python/issues )
1111to 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.
1313In the case of a bug suspiscion, please try to give all the relevant
1414information to allow reproducing the error or identifying
1515its root cause (version of the IMAS-Python, OS and relevant
1616dependencies, snippet of code);
17- 4 . apply relevant labels to the issue.
17+ 3 . apply relevant labels to the issue.
1818
1919## You want to make or ask some change to the code
20201 . use the [ issue search] ( https://github.com/iterorganization/IMAS-Python/issues )
2121to 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
2323implemented and specify it if you intend to work on it yourself or if some help
2424will 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,
2626at which time the issue will be assigned (to you or someone else who can work on
2727this 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
2929profile and create your own feature branch off of the latest develop commit.
3030Make sure to regularly sync your branch with the latest commits from ` develop `
3131(find instructions
3232[ 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
3434[ 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 ) ).
3535
3636
0 commit comments