> Looks like the GH branch protection is kicking in , kind of like : > https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-pull-request-reviews-before-merging > > Alternatively, you could do a PR to the branch (and merge it)?
This should work for what we need to do and avoid the branch protection issues, has this been tried yet? We should keep the release branches protected IMO so they don't get updated without anyone knowing -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm/issues/13586#issuecomment-1416210181 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm/issues/13586/1416210...@github.com>
