-
Notifications
You must be signed in to change notification settings - Fork 369
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/hashicorp/terraform-website/8aHvD8pRXNxgRZYhof8KhcqNAcT7 |
f66cdd3
to
08fd1de
Compare
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.
🥳
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.
left a wording suggestion but otherwise - thank you!
- Log in to circleci.com, and make sure you're viewing the HashiCorp organization. | ||
- Go to the terraform-website project's list of workflows. | ||
- Find the most recent "website-deploy" workflow, and click the "Rerun workflow from start" button (which looks like a refresh button with a numeral "1" inside). | ||
New commits in `hashicorp/terraform` and `hashicorp/terraform-cdk` don't automatically deploy the site. To use the latest upstream content, you'll need to open a PR bumping the submodule commit. |
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.
New commits in submodules like hashicorp/terraform
and hashicorp/terraform-cdk
don't automatically deploy the site and are not automatically reflected when the site is deployed. To deploy the website with the latest content, you need to open a PR in this repository that updates the submodule to point to the latest commit on stable-website
.
This PR overwrites the contents of this repo with the contents of
terraform-website-next
, which is the site that has been servingterraform.io
for a hot minute.Also along for the ride is the migration of our docs from markdown to MDX! 🎉