remove the directory v5.1 #208
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
🚀 IvorySQL-Docs Preview Ready
|
NotHimmel
approved these changes
Jan 30, 2026
|
🚀 IvorySQL-Docs Preview Ready
|
|
🚀 IvorySQL-Docs Preview Ready
|
yuanyl630
force-pushed
the
feat/remove-nested-v5.1-structure
branch
from
bcfe663 to
3195ce1
Compare
|
🚀 IvorySQL-Docs Preview Ready
|
|
🚀 IvorySQL-Docs Preview Ready
|
yuanyl630
force-pushed
the
feat/remove-nested-v5.1-structure
branch
from
6f6c588 to
3195ce1
Compare
|
🚀 IvorySQL-Docs Preview Ready
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When accessing the IvorySQL documentation website, you may notice that the page URL looks a bit unusual. The document version appears twice in the URL—for example:
https://docs.ivorysql.org/en/ivorysql-doc/v5.1/v5.1/welcome
This PR aims to resolve that issue. It also addresses a recurring pain point in each release: avoiding the need to rename a directory and update reference paths for specific documents after creating a new branch for a release—something that PR #194 previously handled.