There was an error while loading. Please reload this page.
1 parent dd8e201 commit e016e4dCopy full SHA for e016e4d
1 file changed
content/changes/2015-09-03-ensure-your-app-is-ready-for-protected-branches.md
@@ -15,7 +15,7 @@ each required status check.
15
16
These restrictions apply to branch manipulations performed via the GitHub API
17
as well. So when you protect a branch, you will no longer be able to [delete
18
-the branch][delete] via the API or perform [update it][update] to point at a
+the branch][delete] via the API or [update it][update] to point at a
19
non-ancestor commit, even with `"force": true`. And if your branch has required
20
status checks, you won’t be able to [update it][update] or [merge pull
21
requests][merge] into that branch until `success` Statuses have been posted to
0 commit comments