Thanks Dan for the pointer! That is useful indeed. Sounds like Julio, instead of creating a copy and archiving the older master branch, you can simply rename using the steps outlined here: https://docs.github.com/en/github/administering-a-repository/managing-branch... -Archana On 7/22/21, 2:17 AM, "Middleton, Dan" <dan.middleton@intel.com> wrote: Hi, I'm new the community, so sorry if I have the wrong context. If the goal is just to rename the branch I believe you can do that automagically now without manual copies and deletes... https://github.com/github/renaming#rename-existing " Renaming a branch will: * Re-target any open pull requests * Update any draft releases based on the branch * Move any branch protection rules that explicitly reference the old name * Update the branch used to build GitHub Pages, if applicable * Show a notice to repository contributors, maintainers, and admins on the repository homepage with instructions to update local copies of the repository * Show a notice to contributors who git push to the old branch * Redirect web requests for the old branch name to the new branch name * Return a "Moved Permanently" response in API requests for the old branch name" Regards, Dan On 7/21/21, 3:32 PM, "Montes, Julio" <julio.montes@intel.com> wrote: Hi kata-folks I'm planning to create a copy of master branch in the govmm[1] repository called main, main will be the principal branch and master will be archived (if this is possible). I will make the changes needed in the kata-containers repository to support the previous change. Please speak up if you see any inconvenience or disagree with that change. Thanks -- Julio [1]: https://github.com/kata-containers/govmm _______________________________________________ kata-dev mailing list kata-dev@lists.katacontainers.io http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev _______________________________________________ kata-dev mailing list kata-dev@lists.katacontainers.io http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev