Updating .morph jobs while task is running

We’re looking at using some automated git processes to push changes to our production space. What are the implications of pushing/overwriting the .morph files while the process is running? I’d assume as it’s just xml, it’s stored in memory and the push/overwrite would work and the process would be changed for the next iteration of the task. But obviously it’s possible the .morph file is locked, or other things may be possible.

Can you give me a brief outline of how this would affect the server?

A .morph file can be updated with a git pull or overwritten without any problems, even when the task is running. They are not locked.

You can even update via git the task definitions themselves (XML files stored in the system folder). However, in this case, it would require forcing updating task definitions in the space settings.