hirosystems / docs

Hiro developer documentation website
https://docs.hiro.so/
34 stars 55 forks source link

Add a GitHub Action to deploy Docs site on-demand #366

Closed sabbyanandan closed 2 months ago

LakshmiLavanyaKasturi commented 1 year ago

We currently have a re-deploy option available in Vercel for a specific build. Image

If we decide to keep the remote docs and automate the process of build trigger, this new issue can address it.

LakshmiLavanyaKasturi commented 1 year ago

@sabbyanandan, Since we already have the option to redeploy, I believe we don't need an extra action written.

sabbyanandan commented 1 year ago

As far as the "redeploy" option pulls all the upstream repo changes for remote-files, yes, let's please close this issue.

LakshmiLavanyaKasturi commented 1 year ago

Using the "redeploy button", the vercel build is successful; however, Netlify is pulling the old cache.

Eg: The Chainhook repo has new doc changes merged into the Chainhook repo. The docs repo pulls those changes using the remote docs plugin using this PR - https://github.com/hirosystems/docs/pull/408.

The vercel build was successful; however, Netlify failed. Pushing a new commit to the docs branch refreshed the Netlify cache, and the build was successful.

LakshmiLavanyaKasturi commented 1 year ago

Depends on #https://github.com/hirosystems/devops/issues/1267

LakshmiLavanyaKasturi commented 1 year ago

Netlify is removed from the build process. hence marking this as complete.

LakshmiLavanyaKasturi commented 1 year ago

Relates to https://github.com/hirosystems/devops/issues/1267