File permissions in repo change on build machines

1

When our repo is cloned by the build servers some of the files have permissions changes that appear as changes on git status. Since our build inspects the state of the git repo to assign a buildstamp, all our builds on render are marked “dirty” because the repo has changes.

Specifically, some files ending in .sh are shown as changing from 644 → 755.

What changes does render apply to our repo before building and how can we prevent that?

2

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

3

We currently set all shell scripts to be executable by default. This is to help users who may have forgotten to set their script to be executable but need to run it in their build process. We may reconsider this behavior in the future, but have no immediate plans to.