From 619f2a8826fab1715027689e92cf319dd8c94361 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Tue, 25 May 2021 15:25:25 -0400 Subject: [PATCH] typo: "banch" --- .../managing-branches-in-your-repository/renaming-a-branch.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch.md b/content/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch.md index 8991e75833..4378bd06c7 100644 --- a/content/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch.md +++ b/content/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch.md @@ -18,7 +18,7 @@ When you rename a branch on {% data variables.product.product_location %}, any U Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name. -{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the banch name is deprecated and suggesting that users migrate to the new branch name. +{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the branch name is deprecated and suggesting that users migrate to the new branch name. ### Renaming a branch