Skip to content

Conversation

@samjewell
Copy link
Contributor

@samjewell
Copy link
Contributor Author

I'm actually opening this PR because I was curious to know if you had any automation here at all, to automatically update this doc page in response to the actual support you have implemented. Doesn't seem to be the case as far as I can tell, reading the file itself and looking at the history of changes on the file, but please let me know. Thanks!

@samjewell samjewell changed the base branch from gitbook-publish to gitbook-dev April 15, 2025 21:34
@samjewell
Copy link
Contributor Author

ah damn. I saw in the readme that I should make the PR into gitbook-dev first, but when I updated the base-branch to that from gitbook-publish I see a LOT of changes. I guess I forked while I was looking at gitbook-publish branch on Github, and I must have landed there from the docs themselves, when I clicked Edit on GitHub.

Long shot, but do you fancy just cherry-picking my commit and merging it in? I wonder if that would be less work than me trying to rebase, across repos.

Copy link
Contributor

@jycor jycor left a comment

Choose a reason for hiding this comment

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

LGTM

@jycor jycor merged commit df62110 into dolthub:gitbook-dev Apr 15, 2025
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