Here you are pushing the main branch rather than a PR branch so instead of pushing a patch event it will push a state announcement event (30618).
Discussion
The warning indicates that at the time (before your push) github was a commit behind the state on nostr. Maybe you force pushed the previous commit directly to github, or more likely their was some sort of error during your last push after it issued the updated state event but before the push to github competed.
Probably the lack of status updates during pushes made you think it was hanging so you exited early. I've added these in son they will be available in v1.5
If any project maintainers comes across this warning when doing a `git fetch`. The easiest thing to do is to add a other commit and push it. It will update the nostr state and the git server. Another way is to add the git server as a remote and push directly to that.
If the warning is `n ahead` it means that someone has pushes commits to the git server and not to nostr. To prevent you inadvertently overiting those commits and lose them forever you can't push conflicting commits. You'll need to add the git server as a remote, pull the commits, which commit you want to be the head and for push to the git served remote and the nostr remote.
That last point is I think what might have happened to me, I probably killed the process before a nostr commit happened and then made another commit. Interesting edge case...