Delete a branch-protection rule

DELETE/api/repos/{owner}/{repo}/branches/{branch}/protection

deleteBranchProtection

Removes the rule keyed on this branch pattern — the plan's rollback story: no rule, no merge gate. Requires admin access on the repository.

Requires authentication using a bearer token or a session cookie — see tokens and scopes.

curl

curl -X DELETE 'https://neosource.dev/api/repos/OWNER/REPO/branches/BRANCH/protection' \
  -H 'Authorization: Bearer $NEOSOURCE_TOKEN'

fetch

fetch("https://neosource.dev/api/repos/OWNER/REPO/branches/BRANCH/protection", {
  method: "DELETE",
  headers: {
    Authorization: "Bearer $NEOSOURCE_TOKEN",
  },
});

Path parameters

ownerrequired: Repository owner or organization slug.
string
reporequired: Repository name.
string
branchrequired: Exact branch name or glob pattern the rule is keyed on (`*` matches within one `/`-segment, `**` crosses segments). Names containing `/` must be percent-encoded (`release%2Fv1`).
string
ownerrequired: string
reporequired: string
branchrequired: string

Responses

204Protection rule deleted

Standard errors

Bodies documented once for the whole API — see standard errors.

400Bad Request — one of: invalid_input
401Authentication required
403Forbidden — one of: forbidden
404Not Found — one of: not_found
409Conflict — one of: already_exists, conflict, non_fast_forward
423Locked — one of: busy
429Rate limited — retry after the `Retry-After` header
500Internal server error
503Service temporarily unavailable / at capacity — retry after the `Retry-After` header
504Gateway timeout — the request exceeded the server's handling budget