tisonkun commented on PR #417:
URL: https://github.com/apache/pulsar-site/pull/417#issuecomment-1433839373

   @visortelle Thanks for your update! I made a patch on your pull request at 
https://github.com/tealtools/pulsar-site/pull/1. Due to the duplicate branch 
name issue, I cannot just edit on your patch XD. Please take a look.
   
   FWIW the branch name issue looks like:
   
   ```
   ╭─tison@mountarch in repo: pulsar-site on  
tealtools/main:refs/pull/417/head via  v19.6.0 took 127ms
   ╰─λ git push
   fatal: The upstream branch of your current branch does not match
   the name of your current branch.  To push to the upstream branch
   on the remote, use
   
   git push origin HEAD:refs/pull/417/head
   
   To push to the branch of the same name on the remote, use
   
   git push origin HEAD
   
   To choose either option permanently, see push.default in 'git help config'.
   
   To avoid automatically configuring an upstream branch when its name
   won't match the local branch, see option 'simple' of branch.autoSetupMerge
   in 'git help config'.
   
   
   ╭─tison@mountarch in repo: pulsar-site on  
tealtools/main:refs/pull/417/head via  v19.6.0 took 1ms
   [🔴] × git push origin HEAD:refs/pull/417/head
   Enumerating objects: 104, done.
   Counting objects: 100% (104/104), done.
   Delta compression using up to 32 threads
   Compressing objects: 100% (84/84), done.
   Writing objects: 100% (94/94), 19.80 KiB | 19.80 MiB/s, done.
   Total 94 (delta 42), reused 9 (delta 3), pack-reused 0
   remote: Resolving deltas: 100% (42/42), completed with 10 local objects.
   To https://github.com/apache/pulsar-site.git
   ! [remote rejected]         HEAD -> refs/pull/417/head (deny updating a 
hidden ref)
   error: failed to push some refs to 
'https://github.com/apache/pulsar-site.git'
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to