Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document drop branch force #7018

Closed
wants to merge 1 commit into from
Closed

Conversation

raddevon
Copy link
Contributor

@raddevon raddevon commented Mar 8, 2024

Added this to the Reference > Administration > Database page since I think it needs to be there. Its canonical home should be on a new Reference > Administration > Branch page. As part of a future PR, I will comb through the docs to update "database" to "branch" wherever appropriate, and I will also add the aforementioned page with a note on the Administration > Database page that "databases" were renamed "branches" in v5.

@raddevon raddevon requested a review from fantix March 8, 2024 16:28
Comment on lines +55 to +56
You may now drop a branch, even if it has active connections by adding
``force``:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need some kind of a warning here to say, this is not usually recommended because it may interrupt ongoing transactions, use with extra caution? @msullivan

@raddevon
Copy link
Contributor Author

I think this one is no longer relevant after the branches documentation I've merged.

@raddevon raddevon closed this Apr 23, 2024
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.

2 participants