GitBook
Changes in Gitbook are not properly reflected, resulting in duplicate README files. #722
Unanswered
Benjamin-SCAYLE
asked this question in
3. Git Sync
Replies: 1 comment
-
|
Hey Benjamin, thank you for your message in our community! This is indeed a bit confusing, I'm not sure I fully understand what is happening there. All of the changes you are making (moving pages, renaming, etc) are happening on GitBook, correct? Do you have an example of a commit where this happened in your repository? Can you please share that at [email protected]? That way we'll be able to ask further questions and understand this issue in more details. I look forward to your feedback! Thank you, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It's a bit challenging to describe this issue, but something doesn't work quite right when renaming or moving pages in Gitbook. Specifically, changes aren't always reflected as expected, which can lead to problems like duplicated README files.
Example:
For example, if a new page (e.g., Release 23.09.) is added above "Release 01.09.," the system may create a "readme (1).md" file in some cases. Moreover, when creating future sections like "October 2024," these duplicated README files are not properly cleaned up, leading to a cluttered and increasingly disorganized file structure.
Beta Was this translation helpful? Give feedback.
All reactions