leandron commented on issue #13586: URL: https://github.com/apache/tvm/issues/13586#issuecomment-1414158464
> The release branches are protected from force pushes / deletes by GitHub, but cherry-picking shouldn't require rewriting history right? Are you doing something like this? > > ```shell > git fetch origin > git checkout v0.11.0 > git cherry-pick 0eabbac2160a8a630e1994969f664ccf6233fc7e > git push origin > ``` I was just trying to produce the tarball with the actual `v0.11.0` with that cherry-picked commit, but I'm probably missing something: ``` % git remote -v origin [email protected]:leandron/tvm.git (fetch) origin [email protected]:leandron/tvm.git (push) upstream [email protected]:apache/tvm.git (fetch) upstream [email protected]:apache/tvm.git (push) % git fetch upstream % git checkout upstream/v0.11.0 % git reset --hard upstream/v0.11.0 HEAD is now at 1d9863470 [TIR] Fix PlanAndUpdateBufferAllocationLocation not visiting constant buffer (#13605) % git cherry-pick 0eabbac2160a8a630e1994969f664ccf6233fc7e [v0.11.0 2f999d62e] [BugFix][UMA] Protect target registration (#13624) Author: Balint Cristian <[email protected]> Date: Fri Dec 16 15:23:26 2022 +0200 4 files changed, 42 insertions(+), 16 deletions(-) % git push upstream v0.11.0 Enumerating objects: 42, done. Counting objects: 100% (42/42), done. Delta compression using up to 8 threads Compressing objects: 100% (19/19), done. Writing objects: 100% (23/23), 3.93 KiB | 3.93 MiB/s, done. Total 23 (delta 18), reused 5 (delta 4), pack-reused 0 remote: Resolving deltas: 100% (18/18), completed with 18 local objects. remote: error: GH006: Protected branch update failed for refs/heads/v0.11.0. remote: error: At least 1 approving review is required by reviewers with write access. Commits must have valid signatures. To github.com:apache/tvm.git ! [remote rejected] v0.11.0 -> v0.11.0 (protected branch hook declined) error: failed to push some refs to 'github.com:apache/tvm.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]
