fix: auto commit and push documentation #815
Merged
Conversation
This file contains 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
|
Planning to review this next week. |
|
I might not get to this today, apologies. |
EvanHahn
approved these changes
Sep 19, 2024
85% sure (I know you can see a preview of the deploy on the PR itself, which is an indication of this?) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To allow publishing the docs site, there's two paths:
push_options: --forceon publish flow after allowing force push on mainI went with the first option since it seemed more straight away.
Options for this were grabbed from here
I think that the only way to try if this works is to merge to main, since main is actually the protected branch. I had to enable force push on that branch from settings, so with enabling that, this should just work
should fix #707