You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tvm.apache.org by "driazati (via GitHub)" <gi...@apache.org> on 2023/02/03 17:55:47 UTC

[GitHub] [tvm] driazati commented on issue #13586: [Release] v0.11.0 release schedule

driazati commented on issue #13586:
URL: https://github.com/apache/tvm/issues/13586#issuecomment-1416210181

   > 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


-- 
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: commits-unsubscribe@tvm.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org