Update build_settings.repo_branch key name
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 323
- Forks
- 133
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 2
Description
An enterprise customer tried to update their production branch with a PATCH to https://api.netlify.com/api/v1/sites/{site_id} and payload {build_settings: {repo_branch: "branch"}}
but our UI makes a PUT to the same endpoints with payload {build_settings: {branch: "branch"}}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the site update endpoint, https://api.netlify.com/api/v1/sites/{site_id}, and inspect the OpenAPI definition for its PATCH and PUT request bodies. Compare the documented build_settings key with the UI's branch payload and the reported repo_branch payload; done means the specification consistently describes the intended key name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100