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.

Sign up for GitHub

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

Jump to bottom

Should be able to self-test this workflow locally #52

Open
Bucknalla opened this issue Feb 14, 2023 · 2 comments · Fixed by #95
Open

Should be able to self-test this workflow locally #52

Bucknalla opened this issue Feb 14, 2023 · 2 comments · Fixed by #95
Assignees
@vipulgupta2048

Comments

@Bucknalla
Copy link
Contributor

Currently there's no mechanism to see how this container works locally; we should have an example directory to be used for self testing to ensure that plugins, such as mermaid and tsdoc (in the future), are still working.
@ab77
Copy link
Member

ab77 commented Apr 1, 2023

Yes, ideally the workflow should create a Docusaurus CF pages site from its README. md

@vipulgupta2048
Copy link
Member

@ab77 We do that already: https://docusaurus-builder.pages.dev/

@vipulgupta2048 vipulgupta2048 linked a pull request Aug 16, 2024 that will close this issue
patch: Exit 1 if docusaurus build fails #95
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vipulgupta2048 vipulgupta2048

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

patch: Exit 1 if docusaurus build fails product-os/docusaurus-builder
3 participants
@ab77 @Bucknalla @vipulgupta2048