Skip to content

Latest commit

 

History

History
42 lines (32 loc) · 1.56 KB

CONTRIBUTING.rst

File metadata and controls

42 lines (32 loc) · 1.56 KB

Thank you for considering contributing to ioppytest!

List of devs and network testers that contributed to the tool:

Federico Sismondi (fsismondi) Constant (cdx) Benjamin (btu) Erwan Le Flem (BhzErlb) Ghada Gharbi (ggharbi) Mahdi Ben Alaya (mbenalaya) Nicolas Le Gall Thijs Walcarius Pauline Gaudet-Chardonnet Miguel Angel Reina ETSI CTI

Git workflow - Merge request guidelines

If you can, please submit a merge request with the fix or improvements including tests. If you don't know how to fix the issue but can write a test that exposes the issue we will accept that as well. In general bug fixes that include a regression test are merged quickly while new features without proper tests are least likely to receive timely feedback. The workflow to make a merge request is as follows:

[1]Fork the project into your personal space on gitlab
[2]Create a feature branch, branch away from master (if it's a fix) or develop (if it's a new feature or doc)
[3]Write tests, code and/or doc
[4]If you have multiple commits please combine them into a few logically organized commits by squashing them
[5]Push the commit(s) to your fork
[6]Submit a merge request (MR) to the master branch / develop branch (depending if it's a fix or new feature)

When having your code reviewed and when reviewing merge requests please take the code review guidelines into account.