Failing with command error on refs/heads/Daverlo-patch-1: failure: Error pushing Action to GitHub Enterprise Server.

[marcellodesales]

time="2025-01-30T00:14:15Z" level=fatal msg="command error on refs/heads/Daverlo-patch-1: failure\nError pushing Action to GitHub Enterprise Server.\ngithub.com/github/codeql-action-sync/internal/push.(*pushService).pushGit\n\t/home/runner/work/codeql-action-sync-tool/codeql-action-sync-tool/internal/push/push.go:250\ngithub.com/github/codeql-action-sync/internal/push.Push\n\t/home/runner/work/codeql-action-sync-tool/codeql-action-sync-tool/internal/push/push.go:491\ngithub.com/github/codeql-action-sync/cmd.glob..func4\n\t/home/runner/work/codeql-action-sync-tool/codeql-action-sync-tool/cmd/sync.go:21\ngithub.com/spf13/cobra.(*Command).execute\n\t/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:985\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\t/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1041\ngithub.com/spf13/cobra.(*Command).ExecuteContext\n\t/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1034\ngithub.com/github/codeql-action-sync/cmd.Execute\n\t/home/runner/work/codeql-action-sync-tool/codeql-action-sync-tool/cmd/root.go:76\nmain.main\n\t/home/runner/work/codeql-action-sync-tool/codeql-action-sync-tool/main.go:15\nruntime.main\n\t/opt/hostedtoolcache/go/1.21.6/x64/src/runtime/proc.go:267\nruntime.goexit\n\t/opt/hostedtoolcache/go/1.21.6/x64/src/runtime/asm_amd64.s:1650"

[chrisgavin]

Hi @marcellodesales. I've not had much luck reproducing this, but I've made a guess that it could be due to pushing a large number of refs in a single request.

I've published a new 1.0.13 release that batches up refs before pushing them, which may make the push more reliable. Feel free to give it try and see if that helps. If not, could you let me know which Enterprise Server version you are pushing to and I will see if I can identify a problem with that particular version.

[marcellodesales]

Hi @chrisgavin to overcome this, I did implement a git fetch, git rebase locally before using the tool... That way, we bypassed this error because I knew it was that specific branch problem... I kept the tool executing right after... I could grab this new version, remove the external sync and verify...

[chrisgavin]

I'm glad you managed to work around this. I'll close this issue, but just let us know if you run into a problem like this again.