-
-
Notifications
You must be signed in to change notification settings - Fork 33
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.
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
Monorepo support #32
Comments
I have same problem with turborepo. Why this action doesn't have additional arguments for this? |
Earlier versions of this action included many options to configure all of the inputs and outputs, but we ended up with many confusing, conflicting configuration options. If anyone has ideas about options we could add to better support monorepos, please let us know! Custom build pipelines with more complex requirements can always accomplish the same thing as this action by adding an additional step after the build runs:
|
I built it manually and uploaded it in the end. https://github.com/nemanjam/nemanjam.github.io/blob/main/.github/workflows/deploy-gh-pages.yml |
Awesome! That is probably the best course of action for now. |
Maybe I am doing something wrong, but I cannot for the life of me deploy from a yarn workspaces monorepo.
I added the base:
It won't build properly because it won't build my other dependencies.
So if I remove the base, it fails because it can't find the
docs/dist
directory.I need a way to build from the root and deploy from a path, but it doesn't seem as though one is exposed.
The text was updated successfully, but these errors were encountered: