Skip to content

Commit 7c17b5f

Browse files
authored
Add 💅
1 parent b3f3d22 commit 7c17b5f

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

content/github/administering-a-repository/renaming-a-branch.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,10 @@ You can rename a branch in a repository on {% data variables.product.product_loc
1515

1616
When you rename a branch on {% data variables.product.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments.
1717

18-
GitHub 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.
19-
2018
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.
2119

20+
{% 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.
21+
2222
### Renaming a branch
2323

2424
{% data reusables.repositories.navigate-to-repo %}

0 commit comments

Comments
 (0)