-
Notifications
You must be signed in to change notification settings - Fork 122
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
Automatic cloud deploy #562
Conversation
docs/.observablehq/deploy.json
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is checked in so that CI and other developers knows they are deploying to the correct project and not overwriting a surprise project.
{name: "Mutables", path: "/javascript/mutables"}, | ||
{name: "Mutables", path: "/javascript/mutables"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prettier did this. I can revert it if you want, but I'm inclined to keep it formatted.
Also, if this goes wrong, we can only tell on main. How do you feel about me just pushing new commits to main until it works, and getting them reviewed after the fact? |
Co-authored-by: Mike Bostock <mbostock@gmail.com>
This won't include the examples in the deploy. The Cloudflare deployed version manually manipulates the dist directory after running build, but we don't have any mechanism to do that in the
observable deploy
command. I'm not sure how we should fix that. I also don't especially want to do it in this PR, since the primary goal for this PR is to get automatic deploys working.