Is there any way to set up production as a git repo instead of a package?

[Valid]

My typical development flow involved making the theme a git repo, make changes, push changes, changes get auto-pulled from git, site is updated.

WP-RIG appears to only provide an 'export' functionality unless I want to run the dev watcher on production (which I imagine would have performance implications)

Any ideas on how I can set this up so that I can make changes to the codebase and have them reflected on the production site without rebundling/uploading?

[Valid]

Update: I've turned off 'compress' so it generates a new theme, and that seems to work decently, but it breaks the site for anyone accessing the it during the build process. Anyone have a more elegant solution?

[digisavvy]

@Valid - I feel like using a CI tool would be a better approach for you, that way you can setup a job that runs your asset builds and then deploys. Have a look at https://branchci.com - it has a recipe for WP Rig.

[jacklowrie]

You could also try Github actions - We set up one at work that runs on every push to main that runs the bundle process, scp's the zip file to our prod environment, then removes the old version of the theme and extracts the new version. As long as you have ssh access to prod, this should work pretty well. For us using WP Engine, the action completes in ~ 2 minutes.