I agree with you approach, but I would like to keep my env set-up away from repo. Limiting the repo only to the application code and env-set up close to the environment where the job runs.

In future, I should be able to run the application in various different environments and every time a change in the env should not update the app code in the repo.