2. Once you have pushed your 1st commit, you can create an associated Merge Request(MR) to your branch. Since the (in MR title add ``Draft: <MR title>`` or check the draft checkbox when creating/editing)
3. Mention the issue associated in the merge request description. This will have as consequence that all the MR associated to an issue will be shown on the issue page. This allows to track the evolution of the progress on a given issue.
3. When the MR is ready remove the part `Draft :` from the title. This allows the reviewers to know when they can review the code.
> :warning: An Issue no longer in Draft: the branch pulled will be from the target branch of the depedencies, if you haven't merge associated work in dependencies, the pipeline mght fail then.
4. When all MR are ready for review. Move the issues from the column ``status::WIP`` to ``status::Review Ready``.
5. Review proces
> :interrobang: **What happens when an MR is no longer in Draft**
> 1. [The branch pulled will be from the target branch of the depedencies, if you haven't merge associated work in dependencies, the pipeline mght fail then.](https://gitlab.eclipse.org/groups/eclipse/aidge/-/wikis/Understand%20the%20CI%20CD%20Pipelines#case-2]
> 2. New jobs will be launched at every pipeline, such as building the project with other additionnal compilers. These jobs can be triggered manually otherwise but are required to run on a non draft pipeline.
4. When MRs in your issue are ready for review. Move the issue from the column ``status::WIP`` to ``status::Review Ready``.
5. Review process
6. Merge MR
7. When every MR is merged, close issue
> :exclamation: Make sure to close every child issue before closing the main issue
