Closed sabbyanandan closed 2 months ago
@sabbyanandan, Since we already have the option to redeploy, I believe we don't need an extra action written.
As far as the "redeploy" option pulls all the upstream repo changes for remote-files, yes, let's please close this issue.
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.
Netlify is removed from the build process. hence marking this as complete.
We currently have a re-deploy option available in Vercel for a specific build.
If we decide to keep the remote docs and automate the process of build trigger, this new issue can address it.