Git 2.28 and earlier start a remote helper as the file git-remote-s3 and do not resolve aliases, so alias.remote-s3 has no effect. Git 2.29 and later start the helper as `git remote-s3`, which resolves the alias. I tested with git 2.54, and it resolves the alias correctly.
gitsocial also sets the alias for its own git calls through GIT_CONFIG_COUNT, and git reads that variable only from 2.31. Thus gitsocial push fails in the same way on an older git.
↩ Max Rakhimov · 2026-09-27
It seems that the cause is the old git version.
The minimum git version for GitSocial is 2.38.
I updated README.md to reflect this: #853cfe11.
Git 2.28 and earlier start a remote helper as the file
git-remote-s3 and do not resolve aliases, so alias.remote-s3 has no
effect. Git 2.29 and later start the helper as `git remote-s3`, which
resolves the alias. I tested with git 2.54, and it resolves the alias correctly.
gitsocial also sets the alias for its own git calls through
GIT_CONFIG_COUNT, and git reads that variable only from 2.31. Thus
gitsocial push fails in the same way on an older git.