You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@godismyjudge95
Yes, I did. My guess is that you can't reference config values from the same config file you're on.
I tested it to on a fresh install of Statamic.
When you run in tinker: config('statamic.git.binary'), you get git.
When you run: config('statamic.git.commands'), you get: [ " add {{ paths }}", " -c "user.name={{ name }}" -c "user.email={{ email }}" commit -m "{{ message }}"", ]
Meaning, the config('statamic.git.binary') is not read from config. Doesn't matter if I set STATAMIC_GIT_BINARY to git, or even hardcode statamic.git.binary to git. The value is always blank when referenced dynamically from statamic.git.commands.
I didn't think you could reference from the same file either, but when I tested that PR it seemed to work. Maybe I had something weird setup and got a false positive. We can check it over.
Bug description
Please see the thread:
https://discord.com/channels/489818810157891584/1240373773279039499/1240374342303350876
for reference.
Autocommit to git fails with messages like:
Replacing
config('statamic.git.binary')
to hardcodedgit
fixes the issue. Most likely this bug was introduced here:770dc48
How to reproduce
Fresh install of Statamic.
Set up git autocommit as per docs.
Make any changes in the entry.
Check application logs for errors.
Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered: