Skip to content

docs: Manage branches guide audit fixes - #6939

Open
danieltprice wants to merge 1 commit into
mainfrom
docs/branches-guide-audit-fixes
Open

danieltprice wants to merge 1 commit into
mainfrom
docs/branches-guide-audit-fixes

Conversation

@danieltprice

Copy link
Copy Markdown
Collaborator
  • Changed the branch expiration examples to a future date.
  • Added that the expiration time must be in the future and within the plan's maximum interval.

NEON PREVIEW

This pull request and its description were written by Isaac.

Co-authored-by: Isaac <no-reply@databricks.com>
@vercel

vercel Bot commented Nov 21, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
neon-next Ready Ready Preview Nov 21, 2026 12:16pm UTC

Request Review

@danieltprice

Copy link
Copy Markdown
Collaborator Author

Live test results

Tested on a throwaway project. Console click paths are static.

Step Result
Create child branch (API, with endpoint) Passed
Create branch (CLI, default parent, --name) Passed
Duplicate branch name rejected Passed
Whitespace-only name rejected Passed
256-character name accepted, 257 rejected Passed
Protect branch; protected branch can't be deleted or reset Passed
Root (default) branch can't be deleted Passed
Rename (CLI and API) Passed
Set and clear expiration (API) Passed
Set default branch (CLI) Passed
neon connection-string with branch, database, and role Passed
Reset from parent (API) Passed
Delete child branch (CLI) Passed
Schema-only branch (CLI --schema-only) Passed
Expiration in the past Rejected (doc example date was in the past)
Expiration limit (maximum interval) Plan-dependent, not fully mapped
Console name limit of 128 characters Not testable (Console)
Root branch allowances per plan Not testable (plan)
Past data (point in time) branch Not run

Doc errors

  • The expiration examples used 2025-08-15, which is in the past. The API rejects it with "expiration time cannot be in the past." The examples now use a future date, and the page says the time must be in the future and within the plan's maximum interval.

This branch was successfully deployed

1 active deployment
Preview – neon-next — e127c99c Deployed Nov 21, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant