# Fcm branch id **URL:** \ **Category:** Rose/Cylc and FCM\ **Created:** [28 October 2025 15:02 UTC](https://cms-helpdesk.ncas.ac.uk/t/fcm-branch-id/1849 "2025-10-28T15:02:00Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![dramauh](https://avatars.discourse-cdn.com/v4/letter/d/c5a1d2/32.png) [@dramauh](https://cms-helpdesk.ncas.ac.uk/u/dramauh)\ **Post date:** [28 October 2025 17:22 UTC](https://cms-helpdesk.ncas.ac.uk/t/fcm-branch-id/1849/5 "2025-10-28T17:22:31Z")
Hi dcase, I am trying to edit NEMO, and I think I found out why I could not use fcm thanks to this [post](https://cms-helpdesk.ncas.ac.uk/t/help-with-making-changes-to-nemo-in-coupled-model/1540/5). However, I’m still a bit unsure about how suite editing works in practice. I followed the UM tutorial, and used the `rosie checkout ` command to bring the suite into my working directory. As I understand it, this creates a local working copy in `~/roses`, which I can edit and run — but those changes remain local unless explicitly committed. My question is: if I modify the suite to make it work in my environment, and someone else later copies the suite (e.g. using `rosie copy` or `rosie checkout`), will my changes be included automatically? Or do I need to commit those changes to the repository first? Thanks in advance for your help — I’m getting a much clearer picture of the process now. --- _[View the full topic](https://cms-helpdesk.ncas.ac.uk/t/fcm-branch-id/1849)._