I’ve noticed that whenever I push updates to GitHub from my v0 project, the executable bit (chmod +x) on my .sh scripts is getting reset. For example, deployment scripts that are executable locally (-rwxr-xr-x) revert to non-executable (-rw-r--r--) after pushing and pulling again.
This suggests that v0’s Git integration or file sync mechanism is not preserving file mode bits, particularly the execute permission in the Git index. In a normal Git workflow, file mode changes (e.g. chmod +x script.sh) are tracked and preserved across pushes and pulls, so this seems to be an unintended behavior.
Can someone from the v0 team confirm whether file permissions are currently being normalized or stripped during commit or sync operations? It would be great if the original execute flags could be preserved to avoid manual re-chmod after each push.